Replies: 2 comments
-
Thanks for the detailed explanation. It would be awesome if
This is a lot of work to implement though. :-) A not so flexible but easier to implement solution could be to add support to
To find the latest run of a task in the master branch, you could then run:
What do you think?
I would be very interested to hear how you use |
Beta Was this translation helpful? Give feedback.
-
idea was implemented here: 0ba69df |
Beta Was this translation helpful? Give feedback.
-
Currently we are using baur to support a CI/CD workflow in a mono repo that potentially has multiple teams working in it at any one time. There are currently around 10 services in the mono repo. We currently just use baur to calculate if a service needs to be built, and the build process is then handed off to Jenkins to produce the artifacts and upload them to Artifactory with metadata.
Every build is stamped with a semantic version that is created using gitversion. The version also includes the short commit sha. A build will then trigger a deployment pipeline to an environment based on what lifecycle it is (PR, merge to master, or tag). Because code deploys are triggered by the build, and because of the version stamping we want to build every time the code changes, even if it's to revert a previous change. This is why we want to use the
diff
command against the most recent build.We do a build and deploy for every PR, and every time there is a push to the PR we build what has changed and deploy that. This is because our automation is still somewhat immature and our QA teams still want to do some manual testing. Because of this we want to keep the baur build data for a PR separate to the builds for master. There are a couple of reasons for this:
To enable this we are using the
--input-str
flag and using the branch or PR name as the string. When we first open a PR we also need something to compare it against so this is where we use the--lookup-input-str
flag with master as the branch, so we can compare against the most recent master builds.The current functionality we are missing is a way of finding the most recent build for a specific branch/input-str rather than the most recent based only on time. Based on the discussions we've had the most sensible option seems to be adding an option to the
baur ls runs
command to look for a build with a specific string input. From there we can get the build number and use the diff command.Beta Was this translation helpful? Give feedback.
All reactions