How to restrict access to my job parameters from my read-only users

[Francisca Munhoz]

Hi guys, I have a Read-only user group on my Jenkins server.

They can not see the config from the jobs if they check parameters 
(/job/MYJOB/123/parameters/) they will be able to see the value. There is a 
way to restrict access to /job/MYJOB/123/parameters/ ?

Or how can I protect this sensitive in the job parameters?

Thanks a lot!
Francisca

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/3c40519c-2270-488b-a6d9-b6b048e17010%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: WARNING: JENKINS-34021: could not get TaskListener in CpsStepContext[435:bat]

[Rinaldo DiGiorgio]

On Wednesday, January 18, 2017 at 9:40:28 AM UTC-5, Rinaldo DiGiorgio wrote:
>
> My log has 100s if not 1000s of the following.
>
>
> Jan 18, 2017 2:32:19 PM 
> org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution 
> logger
> WARNING: JENKINS-34021: could not get TaskListener in 
> CpsStepContext[435:bat]:Owner[9-dev/1942:9-dev #1942]
> java.io.IOException: cannot find current thread
>   at 
> org.jenkinsci.plugins.workflow.cps.CpsStepContext.doGet(CpsStepContext.java:295)
>   at 
> org.jenkinsci.plugins.workflow.support.DefaultStepContext.get(DefaultStepContext.java:61)
>   at 
> org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.logger(DurableTaskStep.java:209)
>   at 
> org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.access$700(DurableTaskStep.java:139)
>   at 
> org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution$3.call(DurableTaskStep.java:308)
>   at 
> org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution$3.call(DurableTaskStep.java:306)
>   at 
> org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution$4.call(DurableTaskStep.java:359)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
>
>
> Any idea how it relates to the code, the exceptions for pipeline are very 
> disconnected from the application.
>
> In the error message above does [bat] mean it is a windows node
>
>
>

I thought the above error was realted to this 
https://issues.jenkins-ci.org/browse/JENKINS-34021  but it is not an NPE
 

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/44be0181-c19f-48cc-8907-42444a4e01af%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline: wildcard for branch name

[David Karr]

On Monday, January 23, 2017 at 9:37:01 AM UTC-8, Sharan Basappa wrote:
>
> Hi,
>
> I am trying to create pipeline script such that it only a certain branches 
> following a naming style are built.
> However, pipeline bails out when I use the wildcard.
>
> The code snippet is below:
>
> stage 'build'
>
> node {
>
> git url: 'git@hd1:testing', branch: test*
>
> sh "pwd"
>
> sh "cat simple.csh"
>
> sh "echo $PATH"
>
> sh "csh simple.csh"
>
> echo("end of pipeline")
>
> }
>
>
> I see the following output from the above script:
>
>
>
> Started by user User
>
>
> [Pipeline] stage (build)
>
>
> Using the ‘stage’ step without a block argument is deprecated
>
>
> Entering stage build
>
>
> Proceeding
>
>
> [Pipeline] node
>
>
> Running on master in /var/lib/jenkins/workspace/test_build_3
>
>
> [Pipeline] {
>
>
> [Pipeline] }
>
>
> [Pipeline] // node
>
>
> [Pipeline] End of Pipeline
>
>
> groovy.lang.MissingPropertyException: No such property: test for class: 
> WorkflowScript
>
>
> at 
> org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:53)
>
>
> at 
> org.codehaus.groovy.runtime.ScriptBytecodeAdapter.getProperty(ScriptBytecodeAdapter.java:458)
>
>
> at 
> com.cloudbees.groovy.cps.sandbox.DefaultInvoker.getProperty(DefaultInvoker.java:33)
>
>
> at 
> com.cloudbees.groovy.cps.impl.PropertyAccessBlock.rawGet(PropertyAccessBlock.java:20)
>
>
> at WorkflowScript.run(WorkflowScript:6)
>
>
> at ___cps.transform___(Native Method)
>
>
> at 
> com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.get(PropertyishBlock.java:74)
>
>
> at 
> com.cloudbees.groovy.cps.LValueBlock$GetAdapter.receive(LValueBlock.java:30)
>
>
> at 
> com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.fixName(PropertyishBlock.java:66)
>
>
> at sun.reflect.GeneratedMethodAccessor725.invoke(Unknown Source)
>
>
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
>
> at java.lang.reflect.Method.invoke(Method.java:606)
>
>
> at 
> com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72)
>
>
> at 
> com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21)
>
>
> at com.cloudbees.groovy.cps.Next.step(Next.java:58)
>
>
> at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:154)
>
>
> at 
> org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:163)
>
>
> at 
> org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:328)
>
>
> at 
> org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$100(CpsThreadGroup.java:80)
>
>
> at 
> org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:240)
>
>
> at 
> org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:228)
>
>
> at 
> org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:63)
>
>
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>
>
> at 
> hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112)
>
>
> at 
> jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
>
>
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>
>
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>
>
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>
>
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>
>
> at java.lang.Thread.run(Thread.java:744)
>
>
> Finished: FAILURE
>
>
> However, when I modify the script as follows:
>
>
> stage 'build'
>
>
> node {
>
> git url: 'git@hd1:testing', branch: test*
>
> sh "pwd"
>
> sh "cat simple.csh"
>
> sh "echo $PATH"
>
> sh "csh simple.csh"
>
> echo("end of pipeline")
>
> }
>
>
> the code executes properly and I get the following output:
>
> Started by user User
>
> [Pipeline] stage (build)
>
> Using the ‘stage’ step without a block argument is deprecated
>
> Entering stage build
>
> Proceeding
>
> [Pipeline] node
>
> Running on master in /var/lib/jenkins/workspace/test_build_3
>
> [Pipeline] {
>
> [Pipeline] git
>
>  > git rev-parse --is-inside-work-tree # timeout=10
>
> Fetching changes from the remote Git repository
>
>  > git config remote.origin.url git@hd1:testing # timeout=10
>
> Fetching upstream changes from git@hd1:testing
>
>  > git --version # timeout=10
>
>  > git fetch --tags --progress git@hd1:testing 
> +refs/heads/*:refs/remotes/origin/*
>
>  > git rev-parse refs/remotes/origin/test^{commit} # timeout=10
>
>  > git rev-parse refs/remotes/origin/origin/test^{commit} # timeout=10
>
> Checking out Revision 264dc398372cba41c026568bd764d2656ebfc511 
> (refs/remotes/origin/test)
>
>  > 

Kubernetes does not show as Cloud Provider

[J]

Hi,

I'm using the latest version of Jenkins (2.32) and the Kubernetes plugin 
(0.10). I've tried re-installing the plugin a few times. My Jenkins is on 
an individual machine. The problem is that it never shows Kubernetes as a 
Cloud Provider (no cloud section in fact); while it works if the docker 
plugin is installed (able to see docker under a cloud section). 

Is this because my Jenkins master isn't installed on a POD itself; although 
I should be able to use jenkins from outside the k8s cluster. Any help 
appreciated. Thanks

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/ad406709-5572-4855-a496-38a83ae53cb6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

LogParserPublisher rules on slave

[jerome]

Hi,

I'm trying to use this pipeline command on my Windows slave node:

step([$class: 'LogParserPublisher', parsingRulesPath: all_rules_file, 
useProjectRule: false, failBuildOnError: true, unstableOnWarning: true, 
showGraphs: true]);

I get the following error:
ERROR: Failed to parse console log

java.io.FileNotFoundException: c:\Jenkins\workspace\MyProject@tmp\all_rules.txt 
(No such file or directory)

The file is created at runtime on the slave, it's there and filled properly 
and permission are correct. I was wondering, if I invoke the step 
LogParserPublisher command, does it get run on the master even if declared 
inside the slave node? do I have to stash/copy the rules files back to the 
master? then do a new node('master') at the end?

if so I will have to send the email after this, so my ig try catch will 
overlap 2 node, is that legal code? and the email will get send by the 
master instead I suppose

Right now I have

node('windows')
{
try
{
...
step([$class: 'LogParserPublisher', parsingRulesPath: all_rules_file, 
useProjectRule: false, failBuildOnError: true, unstableOnWarning: true, 
showGraphs: true]);
...
}
catch(any)
{
currentBuild.result = 'FAILURE'
throw any //rethrow exception to prevent the build from proceeding
}
finally
{
emailext ...
}
}

What I should do to have the LogParserPublisher done back on the master, 
but doesn't seem like ligit code:

try
{
node('windows')
{
...
stash includes: "all_rules.txt", name: 'MyRules'
...
}

node('master')
{
def tempo_dir = pwd([tmp: true])
dir(tempo_dir)
{
unstash name: 'MyRules'
step([$class: 'LogParserPublisher', parsingRulesPath: 
"${tempo_dir}/all_rules.txt", useProjectRule: false, failBuildOnError: 
true, unstableOnWarning: true, showGraphs: true]);
}
}
}
catch(any)
{
currentBuild.result = 'FAILURE'
throw any //rethrow exception to prevent the build from proceeding
}
finally
{
node('master')
{
// I need a node to perform command here but...
emailext ...
}
}


how does one get to send an email if anything failed from any node actions?

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/4c33eb52-5a8d-4277-ada8-579008a4af25%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Bitbucket Branch Source Plugin v2.0.1 SCM API Plugin v2.0.1 is older than required. To fix, install v2.0.2-beta-1 or later.

[Stephen Connolly]

>From my perspective there really were 3 issues that could be seen as
release blockers (the build storm ones) and there were mitigations that
could have been used to address the build storm issues, but due to Time
Zone issues the decision was taken to pull all versions from the update
centre without an opertunity to consult with me.

The other issues are not upgrade blockers but enough people have requested
them that they are being addressed at the same time

Hopefully the releases will be available in the next few days. The SCM API
changes are somewhat exceptional from the normal as we had to do something
rare in the Jenkins community, intentionally break existing plugins - a
result of the bitbucket and GitHub branch source plugins from making
invalid assumptions about internal behaviour of SCM API.

Additionally, these invalid assumptions could result in builds reporting as
building one revision while actually building another revision (mostly
affecting PR-merge builds where the PR has had its target branch changed
after initial index)

So we had to fix the issues but that requires a coordinated release of many
plugins.

Once 2.0.x is out, it should all be much more stable going forward and we
have guidelines for plugin authors to prevent this kind of issue recurring
On Tue 24 Jan 2017 at 19:35,  wrote:

> Wow.  Good to know.
> Now we need a "is it safe to upgrade Jenkins" page somewhere :-)
>
>
>
> On Tuesday, January 24, 2017 at 2:23:15 PM UTC-5, Stephen Connolly wrote:
>
> Please hold... we are working on resolving all the issues in
> https://issues.jenkins-ci.org/browse/JENKINS-41234 before the 2.0.x
> versions of these plugins are returned to the update center
>
>
>
>
>
>
>
>
>
>
>
> --
>
>
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
>
>
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
>
>
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/af8d4ea9-b1fa--8a7f-95748ebd33f6%40googlegroups.com
> 
> .
>
>
> For more options, visit https://groups.google.com/d/optout.
>
>
> --
Sent from my phone

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMw8wAXrpK3JMt4mMup6Q6XvZ%3DfX%2Bna%3DOUgYbe_z_Czzaw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

TFS plug-in 5.2.0 - Plugin

[Eldad Cohen]

Hi All,

I have jenkins 1.6XXX on my Linux Box.
I installed my TFS plug-in 5.2.0.

The get operation copy the files as read only , with a lock sign.
Any suggestions ?

Thanks

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/d01c6e36-04ce-4f0d-9dc3-9e4beefc17ce%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Immediate need Project Manager Health (Domain) - Direct Clien

[Ranadheer Mooli]

*Position Title – Project Manager*

*Worksite Address – Columbia, SC*
*Length of Project – 12+ Months (Extendable)*

*Required Skills (rank in order of Importance): *



· 5 years or more in project management skills

· 5 years project planning experience, including effort estimation
on technical tasks and resource allocation

· 5 years experience working with risk management, including risk
triggers and managing risks to project plan tasks

· Ability to create and document key project management documents
and artifacts



*Preferred Skills (rank in order of Importance): *



· Medicaid or Healthcare Delivery Systems

· Business Analysis experience

· Project Management Professional (PMP) certification

· Scrum Master and/or Product Owner Certification



*Education*



· Bachelors or Master's Degree in Computer Science or related field

-- 
Thanks,
Ranadheer
Swift Solutions Inc
*732.218.7803*  (Desk)
*r...@s3staff.com * (Email)
*www.swiftsol.com * (Website)
Certified Minority Business Enterprise (MBE)

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAEAA5h%2Bk0qsifGR%3DPUnzCHxSg6Odojg%3D7NGW8ZDT28DH4dc_xg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

FileNameFinder().getFileNames fails on one Jenkins node

[Raja Chinnam]

Getting a list of files from jenkins workspace using groovy fails on one 
node but it works on another. How can I investigate it? There was a similar 
error when I tried "new File(pd).eachFile" method but "fileExists 
"$pd\\gol.bat" returned true. 

Pipeline code:

def pd = pwd()
bat "dir $pd"
def bat_files = new FileNameFinder().getFileNames(pd, 'G*.bat')




Output:

C:\Jenkins\Slave\workspace\TestFolder\CodeTestPipe>dir C:\Jenkins\Slave\
workspace\TestFolder\CodeTestPipe 
 Volume in drive C is OSDisk
 Volume Serial Number is AAA1-73FA


 Directory of C:\Jenkins\Slave\workspace\TestFolder\CodeTestPipe


01/23/2017  05:34 PM  .
01/23/2017  05:34 PM  ..
01/23/2017  05:34 PM 4 GOL.bat
   1 File(s)  4 bytes
   2 Dir(s)  134,906,617,856 bytes free
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
C:\Jenkins\Slave\workspace\TestFolder\CodeTestPipe does not exist.
 at org.apache.tools.ant.types.AbstractFileSet.getDirectoryScanner(
AbstractFileSet.java:483)
 at org.codehaus.groovy.ant.FileIterator.setNextObject(FileIterator.java:119
)
 at org.codehaus.groovy.ant.FileIterator.hasNext(FileIterator.java:81)
 at groovy.util.FileNameFinder.getFileNames(FileNameFinder.groovy:44)
 at groovy.util.FileNameFinder$getFileNames.callCurrent(Unknown Source)
 at groovy.util.FileNameFinder.getFileNames(FileNameFinder.groovy:31)
 at groovy.util.IFileNameFinder$getFileNames.call(Unknown Source)
 at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(
CallSiteArray.java:48)
 at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(
AbstractCallSite.java:113)
 at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.methodCall(
DefaultInvoker.java:18)
 at WorkflowScript.run(WorkflowScript:22)
 at ___cps.transform___(Native Method)
 at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(
ContinuationGroup.java:57)
 at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.
dispatchOrArg(FunctionCallBlock.java:109)
 at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(
FunctionCallBlock.java:82)
 at sun.reflect.GeneratedMethodAccessor105.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
 at java.lang.reflect.Method.invoke(Unknown Source)
 at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(
ContinuationPtr.java:72)
 at com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21)
 at com.cloudbees.groovy.cps.Next.step(Next.java:58)
 at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:154)
 at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java
:163)
 at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.
java:324)
 at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$100(
CpsThreadGroup.java:78)
 at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.
java:236)
 at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.
java:224)
 at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(
CpsVmExecutorService.java:63)
 at java.util.concurrent.FutureTask.run(Unknown Source)
 at hudson.remoting.SingleLaneExecutorService$1.run(
SingleLaneExecutorService.java:112)
 at jenkins.util.ContextResettingExecutorService$1.run(
ContextResettingExecutorService.java:28)
 at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
 at java.util.concurrent.FutureTask.run(Unknown Source)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
 at java.lang.Thread.run(Unknown Source)
Finished: FAILURE











-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/dcbe14ca-a944-4486-a6fd-82da65fb75ef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Bitbucket Branch Source Plugin v2.0.1 SCM API Plugin v2.0.1 is older than required. To fix, install v2.0.2-beta-1 or later.

[kyee]

Wow.  Good to know.
Now we need a "is it safe to upgrade Jenkins" page somewhere :-)


On Tuesday, January 24, 2017 at 2:23:15 PM UTC-5, Stephen Connolly wrote:
>
> Please hold... we are working on resolving all the issues in 
> https://issues.jenkins-ci.org/browse/JENKINS-41234 before the 2.0.x 
> versions of these plugins are returned to the update center
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/af8d4ea9-b1fa--8a7f-95748ebd33f6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Bitbucket Branch Source Plugin v2.0.1 SCM API Plugin v2.0.1 is older than required. To fix, install v2.0.2-beta-1 or later.

[Stephen Connolly]

Please hold... we are working on resolving all the issues in
https://issues.jenkins-ci.org/browse/JENKINS-41234 before the 2.0.x
versions of these plugins are returned to the update center

On 24 January 2017 at 18:53,  wrote:

> The available plugins doesn't show a version 2.0.2 of the SCM API
> Plugin...anyone know how to get that to show up?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-users/4ed77bbf-efb0-4246-bfa7-bf0e738b9487%40googlegroups.
> com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMzmrgHSf3rJ2cjpNAu6jGFCDQwkCrrj5PO7gEBZXHqpYw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins jobs on cifs mount drive

[jerome]

I'm currently having some issue with the jobs on a cifs mount for Jenkins. 
The l

ln -s builds/lastStableBuild /var/lib/jenkins/jobs/MyJob/lastStable failed: 13 
Permission denied

The user and group is both set to Jenkins and it can write there for the reste 
of the operation. My guess is that my network share doesn't support "unix 
extensions" into samba, which is not under my control. Anybody ever had this 
problems too?



-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/a024eca5-06de-4803-95a1-25a2b5b3d97b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Pipeline checkout poll argument

[jerome]

Hi,
I just would have some light shed on the poll option when doing a pipeline 
checkout.

I currently have a repos for my jenkinsfile, which I don't want to poll for 
change (but I could poll it if necessary to activate the poll option).
My code reside into another repo, which I would like to poll for change and 
start a build with default parameters value.

I was wondering what are the exact effect of the poll option into the 
checkout pipeline method?

My guess:
- It add the repos to the polling if the polling on the jobs is activate 
(which will also poll the repos of my jenkinsfile).
- I need to start a first build manually so it get register

am I correct on all this or not?

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/16727c0b-c1d8-48ca-945e-cf2f73bd9ffa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Bitbucket Branch Source Plugin v2.0.1 SCM API Plugin v2.0.1 is older than required. To fix, install v2.0.2-beta-1 or later.

[kyee]

The available plugins doesn't show a version 2.0.2 of the SCM API 
Plugin...anyone know how to get that to show up?

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/4ed77bbf-efb0-4246-bfa7-bf0e738b9487%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline: wildcard for branch name

[Indra Gunawan (ingunawa)]

You can’t use the simple git pipeline command if you want to be fancy

You should use the form where you can specify more options like configuring Git 
SCM:

checkout scm: [$class: 'GitSCM', branches: [[name: '*/test*']], 
userRemoteConfigs: [[url: 'git@hd1:testing']]]

From:  on behalf of Sharan Basappa 

Reply-To: "jenkinsci-users@googlegroups.com" 
Date: Tuesday, January 24, 2017 at 9:46 AM
To: Jenkins Users 
Subject: Re: Pipeline: wildcard for branch name

Victor,

I tried all options as follows:


git url: 'git@hd1:testing', branch: "test*"

git url: 'git@hd1:testing', branch: test*

git url: 'git@hd1:testing', branch: 'test*'



In all the 3 cases, Jenkins exits with error. I looked into the log again and 
this is what I see:



Caused by: hudson.plugins.git.GitException: Command "git checkout -b test* 
264dc398372cba41c026568bd764d2656ebfc511" returned status code 128:



stdout:



stderr: fatal: git checkout: we do not like 'test*' as a branch name.


Somehow, Git is trying to checkout a branch with a wildcard which is anyway not 
my intent.
All I wan't is to checkout from a branch which follows naming convention such 
as test* (e.g. testa, testb etc.)

Can someone help?



On Monday, 23 January 2017 23:28:12 UTC+5:30, Victor Martinez wrote:
Test property doesn't exist so, according to the doc:
- https://jenkins.io/doc/pipeline/steps/git/#git-git
-- branch is a string therefore you need to quote it otherwise it seems it's 
recognised as a property

You can also try with the generic scm step, explained also in the same page

Cheers

On Monday, 23 January 2017 17:37:01 UTC, Sharan Basappa wrote:
Hi,

I am trying to create pipeline script such that it only a certain branches 
following a naming style are built.
However, pipeline bails out when I use the wildcard.

The code snippet is below:


stage 'build'

node {

git url: 'git@hd1:testing', branch: test*

sh "pwd"

sh "cat simple.csh"

sh "echo $PATH"

sh "csh simple.csh"

echo("end of pipeline")

}



I see the following output from the above script:





Started by user User



[Pipeline] stage (build)



Using the ‘stage’ step without a block argument is deprecated



Entering stage build



Proceeding



[Pipeline] node



Running on master in /var/lib/jenkins/workspace/test_build_3



[Pipeline] {



[Pipeline] }



[Pipeline] // node



[Pipeline] End of Pipeline



groovy.lang.MissingPropertyException: No such property: test for class: 
WorkflowScript



at 
org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:53)



at 
org.codehaus.groovy.runtime.ScriptBytecodeAdapter.getProperty(ScriptBytecodeAdapter.java:458)



at 
com.cloudbees.groovy.cps.sandbox.DefaultInvoker.getProperty(DefaultInvoker.java:33)



at 
com.cloudbees.groovy.cps.impl.PropertyAccessBlock.rawGet(PropertyAccessBlock.java:20)



at WorkflowScript.run(WorkflowScript:6)



at ___cps.transform___(Native Method)



at 
com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.get(PropertyishBlock.java:74)



at 
com.cloudbees.groovy.cps.LValueBlock$GetAdapter.receive(LValueBlock.java:30)



at 
com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.fixName(PropertyishBlock.java:66)



at sun.reflect.GeneratedMethodAccessor725.invoke(Unknown Source)



at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)



at java.lang.reflect.Method.invoke(Method.java:606)



at 
com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72)



at 
com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21)



at com.cloudbees.groovy.cps.Next.step(Next.java:58)



at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:154)



at 
org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:163)



at 
org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:328)



at 
org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$100(CpsThreadGroup.java:80)



at 
org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:240)



at 
org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:228)



at 
org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:63)



at java.util.concurrent.FutureTask.run(FutureTask.java:262)



at 
hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112)



at 
jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)



at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)



at 

Re: Pipeline: wildcard for branch name

[Sharan Basappa]

Victor,

I tried all options as follows:

git url: 'git@hd1:testing', branch: "test*"

git url: 'git@hd1:testing', branch: test*

git url: 'git@hd1:testing', branch: 'test*'


In all the 3 cases, Jenkins exits with error. I looked into the log again 
and this is what I see:


Caused by: hudson.plugins.git.GitException: Command "git checkout -b test* 
264dc398372cba41c026568bd764d2656ebfc511" returned status code 128:


stdout: 


stderr: fatal: git checkout: we do not like 'test*' as a branch name.


Somehow, Git is trying to checkout a branch with a wildcard which is anyway 
not my intent.
All I wan't is to checkout from a branch which follows naming convention 
such as test* (e.g. testa, testb etc.)

Can someone help?



On Monday, 23 January 2017 23:28:12 UTC+5:30, Victor Martinez wrote:

> Test property doesn't exist so, according to the doc:
> - https://jenkins.io/doc/pipeline/steps/git/#git-git
> -- branch is a string therefore you need to quote it otherwise it seems 
> it's recognised as a property 
>
> You can also try with the* generic scm step*, explained also in the same 
> page
>
> Cheers
>
> On Monday, 23 January 2017 17:37:01 UTC, Sharan Basappa wrote:
>>
>> Hi,
>>
>> I am trying to create pipeline script such that it only a certain 
>> branches following a naming style are built.
>> However, pipeline bails out when I use the wildcard.
>>
>> The code snippet is below:
>>
>> stage 'build'
>>
>> node {
>>
>> git url: 'git@hd1:testing', branch: test*
>>
>> sh "pwd"
>>
>> sh "cat simple.csh"
>>
>> sh "echo $PATH"
>>
>> sh "csh simple.csh"
>>
>> echo("end of pipeline")
>>
>> }
>>
>>
>> I see the following output from the above script:
>>
>>
>>
>> Started by user User
>>
>>
>> [Pipeline] stage (build)
>>
>>
>> Using the ‘stage’ step without a block argument is deprecated
>>
>>
>> Entering stage build
>>
>>
>> Proceeding
>>
>>
>> [Pipeline] node
>>
>>
>> Running on master in /var/lib/jenkins/workspace/test_build_3
>>
>>
>> [Pipeline] {
>>
>>
>> [Pipeline] }
>>
>>
>> [Pipeline] // node
>>
>>
>> [Pipeline] End of Pipeline
>>
>>
>> groovy.lang.MissingPropertyException: No such property: test for class: 
>> WorkflowScript
>>
>>
>> at 
>> org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:53)
>>
>>
>> at 
>> org.codehaus.groovy.runtime.ScriptBytecodeAdapter.getProperty(ScriptBytecodeAdapter.java:458)
>>
>>
>> at 
>> com.cloudbees.groovy.cps.sandbox.DefaultInvoker.getProperty(DefaultInvoker.java:33)
>>
>>
>> at 
>> com.cloudbees.groovy.cps.impl.PropertyAccessBlock.rawGet(PropertyAccessBlock.java:20)
>>
>>
>> at WorkflowScript.run(WorkflowScript:6)
>>
>>
>> at ___cps.transform___(Native Method)
>>
>>
>> at 
>> com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.get(PropertyishBlock.java:74)
>>
>>
>> at 
>> com.cloudbees.groovy.cps.LValueBlock$GetAdapter.receive(LValueBlock.java:30)
>>
>>
>> at 
>> com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.fixName(PropertyishBlock.java:66)
>>
>>
>> at sun.reflect.GeneratedMethodAccessor725.invoke(Unknown Source)
>>
>>
>> at 
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>
>>
>> at java.lang.reflect.Method.invoke(Method.java:606)
>>
>>
>> at 
>> com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72)
>>
>>
>> at 
>> com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21)
>>
>>
>> at com.cloudbees.groovy.cps.Next.step(Next.java:58)
>>
>>
>> at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:154)
>>
>>
>> at 
>> org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:163)
>>
>>
>> at 
>> org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:328)
>>
>>
>> at 
>> org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$100(CpsThreadGroup.java:80)
>>
>>
>> at 
>> org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:240)
>>
>>
>> at 
>> org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:228)
>>
>>
>> at 
>> org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:63)
>>
>>
>> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>>
>>
>> at 
>> hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112)
>>
>>
>> at 
>> jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
>>
>>
>> at 
>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>>
>>
>> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>>
>>
>> at 
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>>
>>
>> at 
>>