Hi Bamboo-Guru,
I wonder what is the best approach in the current situation;
In our project we have a set of build, deploy and test jobs. In the nightly build, which takes the full test set (which takes a couple of hours), can eventually can lead to a releasable build
The on-commit build though, uses the same build, deploy and smaller set of test jobs, and is mainly used to provide CI feedback to the developers.
Would there be a way to set this up in 1 flow where only the nightly triggered build takes up all the test jobs, and the on-commit builds to only uses the smaller test set?
This will definitely impact the maintainability of the pipelines, where on changes we don't want to do things twice.
Thanks for providing feedback for us,
Sergey
Hi Sergey,
In my opinion, I guess it would be better if you have two different plan in one project. As for trigger, it will run the build for the whole plan and can't be specified by only stages. Therefore if you have sets of jobs that specific to specifc trigger, I would suggest you to have two different plans.
Hope it helps.
I had an additional answer but after rethinking it, it it was not correct :).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Validate your expertise in managing Jira Service Projects for Cloud. Master configuration, optimize workflows, and manage users seamlessly. Earn global 🗺️ recognition and advance your career as a trusted Jira Service management expert.
Get Certified! ✍️Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.