|
Santiago Chialvo opened 7 months ago
|
|||||||||
|
Robin Shen changed fields 7 months ago
|
|||||||||
|
|
Thanks for the kind words. This turns out to be a bug. As to yml update, builds will always be linked to state of the yml when it is generated. That is, code and its build logic are from same commit. This is key for ci/cd as code, and is essential to make build reproducible and predictable. |
|||||||||
|
|
Hi Robin, Thanks for the quick response. I'm glad it turned out to be helpful to report this bug. About yml, thanks for that. What would you think or recommend as the simplest approach to add a build version number (similar to what you do in buildVersion: '@file:buildVersion@' in this project yml) but for our project where we create builds with the only purpose of uploading artifacts? Might be hardcoding the 'buildVersion' value in the yml for each commit the simpler solution? |
|||||||||
|
|
@etekken09 you may create a file in git to store build version, and use that file to set build version. This has the advantage that build version is also git tracked. If this job should only be manually triggered, another approach is to define a parameter in your job to prompt for a text value, and use that value as build version. |
|||||||||
|
OneDev changed state to 'Closed' 7 months ago
|
|||||||||
|
|
State changed as code fixing the issue is committed (8f447c45) |
|||||||||
|
Referenced from commit 7 months ago
|
||||||||||
|
|
Hi Robin,
Thanks, is there an example yml here on any other project you can point me so I can take a look on this approach? |
|||||||||
|
|
Please check this tutorial: |
|||||||||
|
|
OneDev changed state to 'Released' 7 months ago
|
|||||||||
|
|
State changed as build #4221 is successful |
|||||||||
|
|
Robin, Thank you very much, it works excellently as expected. Regards, Santiago. |
| Type |
Bug
|
| Priority |
Normal
|
| Assignee | |
| Affected Versions |
<=9.2.0
|
| Labels |
No labels
|
Hi everyone,
Thanks for this amazing tool, we've using it intensely over the last couple of months, and it works wonderfully. However, when creating builds we have an issue with artifacts (we upload them manually), and it is not possible to upload multiple artifacts/files at once (at least it doesn't work for us). When we drop multiple files here:
and click Upload, it always shows an error. This is annoying since you need to upload one by one and wait each time (also waiting time might be truly slow, and frequently ends in error too). Is this normal behavior, or is there any way to improve it?
P.S: Non-related question, but also we're wondering: once we update yml file with new steps/commands, is it possible to re-run older builds so these new steps are considered now, or that build is linked forever to the state of the yml at that moment?
Thanks!
Santiago.