Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Arcade publish using release pipelines #2236

Merged
merged 5 commits into from
Mar 13, 2019
Merged

Conversation

@JohnTortugo JohnTortugo self-assigned this Mar 13, 2019
Copy link
Member

@chcosta chcosta left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is great.

How do you know (or get notified) which Release pipeline contains your changes and is scheduled as a result of publishing?

@JohnTortugo
Copy link
Contributor Author

This is great.

How do you know (or get notified) which Release pipeline contains your changes and is scheduled as a result of publishing?

The release pipeline(s) run are the ones associated with the build's channel(s). I believe that this doesn't change very often but I agree that this should be easier to know..

Right now the only way to know which release correspond to your build is by going to the pipeline page (for instance) and looking it up - the release contains the build-def name and build-number as title.

There still a few things to be implemented to make easier for the user to know what's going on during/after publishing. I'll send an e-mail around to talk about that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants