-
OneDev 10.6 modified behavior of build in the way that triggering of a job will be ignored if it is already fired with same commit and param. If you need to trigger the job repeatedly, please create an optional param for that job, and then trigger the job each time with a different param (timestamp for instance).
-
Previous Value Current Value Open
Closed
-
Thanks for the quick response and sorry for opening an issue, I didn't get this change from the release notes. Works now!
Keep up the great work on this software!
Best regards Armin
| Type |
Bug
|
| Priority |
Major
|
| Assignee | |
| Affected Versions |
10.6.0
|
| Labels |
No labels
|
Issue Votes (0)
Hello Robin,
I was upgrading my instance from 8.3.8 to 10.6.0 directly - upgrade run smoothly. Although, I cannot make job triggers run via REST API as described here.
The strange thing is that the GET request (unchanged, same as before) to
~api/trigger-jobstill responses with 200 and the next build number, but the build is not invoked. There's no error log or anything as it seems to be successful, but no job is running.Has something changed, I couldn't spot anything in this regard in the release notes.
Thanks for any feedback on the issue, this is currently blocking my CI/CD pipeline.
Note: The build invocation when pushing with git works normally, it seems to be a pure Rest API problem.
I've added a server log which contains some errors, but I think they're not related, but maybe you can make better readings out of it:
Armin