Hi all,

Just heads-up, we have applied a hotfix to Jenkins Pipeline library in 
order to stabilize **SOME** of the plugin Pipelines. 
https://github.com/jenkins-infra/pipeline-library/releases/tag/1.2.0. What 
does the patch do?

   - buildPlugin() now enforces ACI for Linux flows
   - buildPlugin() now skips Windows configurations


   - all other methods are not fixed. runPCT(), runATH(), essentialsTest() 
   and so on will not work
   - Jenkins core build swill keep failing
   -  ACI agents do not offer Docker on Linux nodes. Any flow using Docker 
   CLI will fail. (e.g. Docker fixtures from Jenkins Test Harness)

Anyway, this change should help some plugin maintainers. 

BR, Oleg

P.S: I have enabled changelog for Jenkins Pipeline Library this week. If 
you are interested to get notifications for changes happening there, please 
feel free to subscribe to https://github.com/jenkins-infra/pipeline-library

On Thursday, August 15, 2019 at 5:33:16 PM UTC+2, R. Tyler Croy wrote:
> I'm writing this to let you all know that we're experiencing on on-going 
> partial outage on ci.jenkins.io which is affecting the ability of the 
> system to 
> process pull requests and merges to plugins, core, etc. 
> Starting sometime yesterday (2019-08-14), all attempts to provision Azure 
> VM 
> agents began failing with Azure API errors. As such **no** Azure VM agents 
> are 
> provisioning. Fortunately Azure Container Instances are provisioning, so 
> now 
> might be a good time to try them out for pull requests you wish to 
> validate: 
> buildPlugin(useAci: true) will utilize those agent types for the Linux 
> branches 
> of the pipeline. 
> I have some backchannel communication going on with some teams at 
> Microsoft 
> about the issue, but at this time I do not have an estimated time for 
> resolution. 
> The underlying cause appears that the Azure REST APIs that ci.jenkins.io 
> are 
> relying on are rather old, no longer supported, and something may have 
> changed 
> to cause them to start failing to validate the "Deployments" (Azure 
> terminology) generated by the plugin which integrates Jenkins to Azure. If 
> my 
> suspicions are correct about the fix, it will require some new plugin 
> builds 
> and releases, which would mean we're likely a day or two away from the 
> issue 
> fully being resolved. 
> I will update this thread as more information becomes available. 
> Cheers 
> -- 
> GitHub:  https://github.com/rtyler 
> GPG Key ID: 0F2298A980EE31ACCA0A7825E5C92681BEF6CEA2 

You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 

Reply via email to