Skip to content
This repository has been archived by the owner on Jul 24, 2024. It is now read-only.

Support Page to also collect integration source code and binary artifacts #4204

Closed
tmielke opened this issue Dec 4, 2018 · 5 comments
Closed
Labels
cat/feature PR label for a new feature closed/migrated notif/triage The issue needs triage. Applied automatically to all new issues. source/pm status/never-stale Marker that this issue should not be marked as stale

Comments

@tmielke
Copy link

tmielke commented Dec 4, 2018

See also https://issues.jboss.org/browse/ENTESB-11574

This is a...


[x ] Feature request
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  
[ ] Documentation issue or request

Description

Please let the Syndesis Help -> Support Page also collect and zip up

  • the source code of the integration (i.e. zip up /tmp/src/src on the pod that runs the integration)
  • the binary application files (i.e. zip up /deployments folder on the pod that runs the integration)

for every integration selected.
This will greatly help in analysing customer problems.
The Support Page currently captures neither of the two above and therefore does not seem to collect any information about the routes being deployed.

@pure-bot pure-bot bot added the notif/triage The issue needs triage. Applied automatically to all new issues. label Dec 4, 2018
@tmielke
Copy link
Author

tmielke commented Dec 4, 2018

This is in relation to syndesisio/syndesis-project#135

@heiko-braun heiko-braun added the cat/feature PR label for a new feature label Dec 4, 2018
@heiko-braun heiko-braun removed the notif/triage The issue needs triage. Applied automatically to all new issues. label Dec 13, 2018
@heiko-braun heiko-braun added this to the Sprint 41 (2/4) milestone Jan 28, 2019
@zregvart
Copy link
Member

zregvart commented Jan 28, 2019

The problem is that we need to access the Maven project we provide to the S2I binary build and it's only accessible (currently) in a running integration POD or in the build image.
Accessing it from a running integration pod could be difficult in cases when the user needs support, i.e. the integration could be crashing and accessing it could be a race to access the files while the integration is still running.
We could either:

  • access the files from the build image (for example spin up a build with custom logic to copy the files)
  • run the integration pod in debug mode (if we can do that without requiring additional permissions)
  • store the provided Maven project when we generate it for the S2I build

We also might consider creating a tool that can create a Maven project for the integration from an integration export or a support ZIP file.

@KurtStam KurtStam reopened this Feb 6, 2019
@heiko-braun heiko-braun removed this from the Sprint 41 (2/4) milestone Feb 18, 2019
@stale
Copy link

stale bot commented May 19, 2019

This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions!

@stale stale bot added the status/stale Issue considered to be stale so that it can be closed soon label May 19, 2019
@stale stale bot closed this as completed May 26, 2019
@tmielke
Copy link
Author

tmielke commented Jul 3, 2019

Any chance to reopen this one?

@heiko-braun heiko-braun reopened this Jul 3, 2019
@stale stale bot removed the status/stale Issue considered to be stale so that it can be closed soon label Jul 3, 2019
@heiko-braun heiko-braun added notif/triage The issue needs triage. Applied automatically to all new issues. and removed notif/triage The issue needs triage. Applied automatically to all new issues. labels Jul 3, 2019
@zregvart zregvart added the status/never-stale Marker that this issue should not be marked as stale label Jul 3, 2019
@heiko-braun
Copy link
Collaborator

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
cat/feature PR label for a new feature closed/migrated notif/triage The issue needs triage. Applied automatically to all new issues. source/pm status/never-stale Marker that this issue should not be marked as stale
Projects
None yet
Development

No branches or pull requests

4 participants