WARNING; this configuration doesn’t seem to delete old builds. Ever, see; https://issues.jenkins-ci.org/browse/JENKINS-34738. I’ve worked around it by putting the following blurb near the top of my JenkinsFile // https://issues.jenkins-ci.org/browse/JENKINS-34738 // https://stackoverflow.com/questions/35370810/how-do-i-use-jenkins-pipeline-properties-step/35471196#35471196 properties ( [ [ $class: 'BuildDiscarderProperty', strategy: [ $class: 'LogRotator', artifactDaysToKeepStr: '14', artifactNumToKeepStr: '3', daysToKeepStr: '14', numToKeepStr: '3' ] ] ] ) This is just a “victory dance” sort of post about setting up a multi-branch build, for a Mercurial project, from a JenkinsFile.
Have you used TortoiseHG? It is lovely! Have you used Cmder? It is lovely! If you … setup cmder to launch from the command line open TortoiseHG Workbench > File / Settings > TortoiseHG / Shell put cmder %(root)s into the Shell field … then you can have these two lovely tools holding hands and kicking-bugs!
This seemed a lot longer when I planned it in my notebook at lunch. GitHub user project (both sides) BitBucket user SCM Schedule ocornut imgui g-pechorin None Periodic Install hg-git You’ll have to do this on the Jenkins server You’ll have to do it either for the Jenkins user or all I’m using an OsX machine as my host, so I was able to use easy_install to install hg-git and dulwich setup a project on GitHub create a Jenkins Freestyle project which runs periodically Polling the SCM was NOT an option since there’s no default branch on GitHub … this is a quirk of hg-git … I think … IIRC/YRMV - so sling me a tweet or whatever if I’m wrong program the job to pull from git, push to hg, and ignore results of 1
I’m still trying to catch up on stuff following Develop. I’ve decided to write a post about my experience(s) switching my work over to SubRepos. I am unaware of the “reason” why they’re considered “bad.” Perhaps it’s a Unix thing? Maybe they don’t work as well as people feel that they should? Whatever I have a (secret) project called “nite-nite/” in which I use and develop some public-domain headers. I want this public-domain stuff to be … well … public-domain and visible to all.