a new version of the config-file-provider (2.15.3) fixing this issue is
released, but unfortunate the update center seems not yet to have picked up
the new version :(
/Domi
On Thursday, January 5, 2017 at 3:20:53 PM UTC+1, Sigbjørn Tvedt wrote:
>
> Hi.
> We tried to upgrade our jenkins instance
Hello All,
I am new to Jenkins and I want to implement continuous delivery pipeline.
We are currently using git for version control and having following git
workflow model
release (stable branch)
main (stable branch)
integration (stable branch)
f1 (feature branch - will come and go according
Hello All,
Need help with pipeline build error in this setup:
Jenkins v2.36 with standard pipeline plugins + configFileProvider plugin
Here is the content of Jenkinsfile, pipeline script:
node('master') {
stage(' == Capitals == ') {
configFileProvider
We use both in our primary Jenkins environment, though folders are the
primary organizing mechanism.
The views are treated more like convenient "favorites" lists of jobs.
Brian
On Sunday, January 8, 2017 at 5:49:36 PM UTC-8, Brian Ray wrote:
>
> To name a few advantages, you can associate crede
To name a few advantages, you can associate credential stores and Pipeline
shared libraries with folders so that they are visible only to the jobs
they contain. Through the Role Strategy plugin, you can also assign various
privileges--and not simply read privileges--to jobs inside different
fol
To name a few advantages, you can associate credential stores and Pipeline
shared libraries with folders so that they are visible . Through the Role
Strategy plugin, you can also assign various privileges--and not simply
read privileges--to jobs inside different folders.
I don't think you can d
No, it is not. You can put the contents of the steps block into a library
function and call that, but not the entire stage or stages blocks.
A.
On Sat, Jan 7, 2017 at 10:52 PM Dan Tran wrote:
>
> Hi
>
> is it doable to place "stages" block into a jenkinsfile lib for reuse
> purpose? if possible
Hi,
using v2.38 of Jenkins
using v1.35 of docker build step plugin
A job that I had setup worked with previous versions of both Jenkins and
the plugin. Since various upgrades, they no longer do.
So now I get
[Docker] INFO: Sucessfully created image groovytest-25:jenkins[Docker] INFO:
created c
