Hi there,

in our build description, we have dedicated build jobs (f.e. "Build for Windows in Release", "Build for Linux in Debug") and jobs that depend on these build jobs (like "Build all in Release"), which depend on the individual jobs and thereby trigger them. Our "Build all"-job is cron triggered.

We now have the issue that OneDev will not run the individual jobs when there were no changes to the repository itself since the last build. We have to run them, though, since some dependecies (like external libraries) might have updated.

I am aware that I can run the individual jobs via cronjob instead, but I wanted to ask if there's a more "elegant" solution to this - something like "invalidate previous builds"-step or a "force rebuilding dependencies"-step that I could add to my build-all-jobs instead.

And while I'm already here: is there an option to prevent users from running a build job by hand? (Scenario: our cronjob'd builds are publishing their artifacts to our staging server for distribution and I don't want users to change the published builds manually by rebuilding them. They still should be able to run builds jobs that do not publish artifacts, though.)

Thanks, Sebastian