Advertisement
jimklimov

jenkins git-scm woes

Dec 7th, 2020
81
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 0.73 KB | None | 0 0
  1. New problem with Jenkins freestyle jobs, of which we have a few, after upgrading to this week's newest core (2.269) and plugins (git-4.4.6 in particular). While pipeline jobs work, the freestyle ones insist that the "Source Code Management" is "None" despite having the tag in config.xml on disk.
  2.  
  3. This happens both in Web-UI (where I first assumed this is related to divs-vs-tables migration since that UI is pretty broken at the moment), but also happens when a job config is saved - the tag is lost and replaced by nullSCM (Job Config history reverting to an older config, Extensible Arguments saving a new option value, etc.), and during run-time parsing of the job to actually run it - git is not called, and jobs fail with no code to build.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement