Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
2nd workflow
-
Hi
My application that has 2 workflows and 2 automated builds.
One workflow is configured to be activated if the SCCM detects a check in - that works fine. This work flow is the standard release cycle of integration , test and production.
I also have a regression cycle that takes the current checked in code and executes some long running tests code overnight against a different database to the other workflows. This workflow is not executed. There are no messages.
However if set the failing Recurring Automated build to the first workflow - it is triggered.
Why won't the 2nd workflow trigger? Do I need another extension, is this a configuration issue or bug?
I have the following extensions to the express version:
Unlimited Automatic Builds Upgrade,Multiple Promotion Workflows Upgrade,Unlimited Environments,
Unlimited ApplicationsThanks
Product: BuildMaster
Version: 4.0.9 -
Do you have a Release created for the secondary workflow?
-
No I don't, I could not see an option - How do I do that?
-
You'll want to CREATE A NEW RELEASE.
You may need to enable "Enable Multiple Active Releases" on the Application Settings Page for the NEW RELEASE option to appear,
-
Ok done that. I now have 2 releases one set to standard, the other set to my alternative workflow.
How do I handle release numbers? Can I give the new relase the same as my standard release? If I give it to one that is less it is cancelled.
-
There are some workflow rules you can adjust for dealing with that (auto close release, auto deploy release, etc).
-
OK they are now triggering. Thanks.
Please can you advise on how to manage the release numbers
For the regression test I entered a release number one higher than the current release on the standard. In reality my regression release will never go into production.
The regression Test workflow is set to a loose Automatic Release Close-Out and disabled Release Cancellation. But the standard workflow is set to strict on all these.
When the standard workflow is released into production, will it cancel my regression release.
Should I set the regression release to a much high number or will this screw up the standard release numbering?
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login