Re: Blueocean - Cloud Foundry plugin for Jenkinsfile pipeline

2017-02-07 Thread Sekhar Kari
Thanks James, I actually did this before. 
When I tried the I see that the volume gets over-written and some how the 
CF executable is still missing from the new image. Below is my Dockerfile. 
I see that the curl script downloaded and extracted the cf tool, but there 
are some intermittent containters being deleted and the final image never 
had the cf in it. 


#

# Create an image for jenkins blueocean version along with CF CLI installer

#

FROM jenkinsci/blueocean:latest


WORKDIR /var/jenkins_home/

RUN curl -L 
"https://cli.run.pivotal.io/stable?release=linux64-binary=github; | 
tar -zx





On Monday, February 6, 2017 at 12:16:36 PM UTC+5:30, James Dumay wrote:
>
> You will need to customize the Blue Ocean image to contain the cf 
> executable and use your new image instead of the one we provide.

-- 
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/43043c6e-3d79-4a3b-a431-d03840cf461b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Reg: Error with weblogic12.1.3 Integration with jenkins

2017-02-07 Thread mukul jha


*A problem occurred while processing the request. Please check our bug 
tracker to see if a similar problem has already been reported. If it is 
already reported, please vote and put a comment on it to let us gauge the 
impact of the problem. If you think this is a new issue, please file a new 
issue. When you file an issue, make sure to add the entire stack trace, 
along with the version of Jenkins and relevant plugins. The users list 
might be also useful in understanding what has happened.*

 

Stack trace

 

javax.servlet.ServletException: java.lang.RuntimeException: Unable to load 
file

  at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796)

  at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)

  at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649)

  at org.kohsuke.stapler.Stapler.service(Stapler.java:238)

  at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)

  at 
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812)

  at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669)

  at 
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135)

  at 
hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:126)

  at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)

  at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:80)

  at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)

  at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)

  at 
hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)

  at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)

  at 
jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117)

  at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)

  at 
org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)

  at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)

  at 
org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)

  at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)

  at 
org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)

  at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)

  at 
jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93)

  at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)

  at 
org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)

  at 
hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67)

  at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)

  at 
hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)

  at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:171)

  at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)

  at 
org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49)

  at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)

  at 
hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:82)

  at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)

  at 
org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30)

  at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)

  at 
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585)

  at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)

  at 
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:553)

  at 
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223)

  at 
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127)

  at 
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)

  at 
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)

  at 
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061)

  at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)

  at 
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)

  at org.eclipse.jetty.server.Server.handle(Server.java:499)

  at 

Re: Issue with pipeline

2017-02-07 Thread Sharan Basappa
If you see the sequence of commands, you will notice that I have used pwd.
Let me list files and see if I can find anything

On Wednesday, 8 February 2017 02:09:54 UTC+5:30, David Karr wrote:

> On Tuesday, February 7, 2017 at 10:15:06 AM UTC-8, Sharan Basappa wrote:
>>
>> Hi All,
>>
>> I am having some trouble executing basic shell commands (highlighted in 
>> red). I cant figure out the issue. Need some help. This is what I get:
>>
>> Branch indexing
>>
>> > git rev-parse --is-inside-work-tree # timeout=10
>>
>> Setting origin to git@hd1:testing
>>
>> > git config remote.origin.url git@hd1:testing # timeout=10
>>
>> Fetching origin...
>>
>> Fetching upstream changes from origin
>>
>> > git --version # timeout=10
>>
>> > git fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/*
>>
>> Seen branch in repository origin/master
>>
>> Seen branch in repository origin/test
>>
>> Seen branch in repository origin/test1
>>
>> Seen branch in repository origin/testx
>>
>> Seen 4 remote branches
>>
>> > 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/*
>>
>> Checking out Revision eb966a50720c888113925000ad9179c79b1c187b (test1)
>>
>> > git config core.sparsecheckout # timeout=10
>>
>> > git checkout -f eb966a50720c888113925000ad9179c79b1c187b
>>
>> > git rev-list eb966a50720c888113925000ad9179c79b1c187b # timeout=10
>>
>> [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/an_example_test1-24PKZ6E7JM3ZFPAWUPX5ZXTQQLVB7HDDUSAFFRMP6IX3XZERQFTA
>>
>> [Pipeline] {
>>
>> [Pipeline] sh
>>
>> [an_example_test1-24PKZ6E7JM3ZFPAWUPX5ZXTQQLVB7HDDUSAFFRMP6IX3XZERQFTA] 
>> Running shell script
>>
>> + pwd
>>
>>
>> /var/lib/jenkins/workspace/an_example_test1-24PKZ6E7JM3ZFPAWUPX5ZXTQQLVB7HDDUSAFFRMP6IX3XZERQFTA
>>
>> [Pipeline] sh
>>
>> [an_example_test1-24PKZ6E7JM3ZFPAWUPX5ZXTQQLVB7HDDUSAFFRMP6IX3XZERQFTA] 
>> Running shell script
>>
>> + cat simple.csh
>>
>> *cat: simple.csh: No such file or directory*
>>
>
> When I run into issues like this, I often will run "sh('pwd')" and 
> "sh('ls')" in the script, to verify exactly where I think I am, and what 
> else is in the directory. The output from those should help.
>  
>
>> [Pipeline] }
>>
>> [Pipeline] // node
>>
>> [Pipeline] End of Pipeline
>>
>> ERROR: script returned exit code 1
>>
>> 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/88f5e782-db7f-4df1-8c3f-fb822bfcd904%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Declarative Pipeline] Using Dockerfile not in root of checkout

2017-02-07 Thread Staffan Forsell
Ok, thx. I will test it as soon as it's merged/released.
/S

On Monday, 6 February 2017 12:57:56 UTC+1, Andrew Bayer wrote:
>
> I've got a PR up for this now - 
> https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/107
>
> A.
>
> On Sun, Feb 5, 2017 at 9:01 PM, Staffan Forsell  > wrote:
>
>> Hmmm, of course I found 
>> https://issues.jenkins-ci.org/browse/JENKINS-41668 a couple of minutes 
>> later...
>>
>> On Sunday, 5 February 2017 20:50:16 UTC+1, Staffan Forsell wrote:
>>>
>>> I have an normal pipeline that looks like this:
>>>
>>> #!groovy
>>> node('docker_host') {
>>>   stage("checkout") {
>>> p4sync credential: 'superSecretCred', depotPath: '//path'
>>>   }
>>>   def myEnv
>>>   stage("docker build") {
>>> myEnv = docker.build("mytag", "utils/docker")
>>>   }
>>>   myEnv.inside {
>>> stage("build") {
>>>   sh "./gradle"
>>> }
>>> } 
>>> }
>>>
>>> It builds a docker image and run the build stage in this image. The only 
>>> non-standard stuff is that the Dockerfile is not in the root but in the 
>>> "utils/docker" subdir to reduce the build context for docker.
>>> I'm trying to convert this to a declarative pipeline but I can't find a 
>>> way to get it to accept the Dockerfile in a separate dir. Normally this is 
>>> done by adding the "utils/build" at the end of the docker build command.
>>> My converted attempt looks like this:
>>>
>>> pipeline {
>>>   agent {
>>> label "docker_host"
>>>   }
>>>   stages {
>>> stage("Checkout") {
>>>   steps {
>>> p4sync credential: 'superSecretCred', depotPath: '//path'
>>>   }
>>> }
>>> stage("Echo world") {
>>>   agent {
>>> dockerfile {
>>>   label "docker_host"
>>>   args "utils/docker"
>>>   // dockerfile "utils/docker/Dockerfile"
>>> }
>>>   }
>>>   steps {
>>> sh "./gradle"
>>>   }
>>> }
>>>   }
>>> }
>>>
>>> This fails with 
>>> java.io.IOException: java.io.FileNotFoundException: 
>>> /jenkins/workspace/test-job-declarative@2/Dockerfile (No such file or 
>>> directory)
>>> at 
>>> hudson.remoting.FastPipedInputStream.read(FastPipedInputStream.java:169)
>>> at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:283)
>>> at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:325)
>>> at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:177)
>>> at java.io.InputStreamReader.read(InputStreamReader.java:184)
>>> at java.io.Reader.read(Reader.java:140)
>>> at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:2001)
>>> at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:1980)
>>> at org.apache.commons.io.IOUtils.copy(IOUtils.java:1957)
>>> at org.apache.commons.io.IOUtils.copy(IOUtils.java:1907)
>>> at org.apache.commons.io.IOUtils.toString(IOUtils.java:778)
>>> at org.apache.commons.io.IOUtils.toString(IOUtils.java:803)
>>> at 
>>> org.jenkinsci.plugins.workflow.steps.ReadFileStep$Execution.run(ReadFileStep.java:89)
>>> at 
>>> org.jenkinsci.plugins.workflow.steps.ReadFileStep$Execution.run(ReadFileStep.java:81)
>>> at 
>>> org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47)
>>> at hudson.security.ACL.impersonate(ACL.java:221)
>>> at 
>>> org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44)
>>> 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:745)
>>> Caused by: java.io.FileNotFoundException: 
>>> /jenkins/workspace/test-job-declarative@2/Dockerfile (No such file or 
>>> directory)
>>> at java.io.FileInputStream.open0(Native Method)
>>> at java.io.FileInputStream.open(FileInputStream.java:195)
>>> at java.io.FileInputStream.(FileInputStream.java:138)
>>> at hudson.FilePath$33.invoke(FilePath.java:1789)
>>> at hudson.FilePath$33.invoke(FilePath.java:1782)
>>> at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2772)
>>> at hudson.remoting.UserRequest.perform(UserRequest.java:153)
>>> at hudson.remoting.UserRequest.perform(UserRequest.java:50)
>>> at hudson.remoting.Request$2.run(Request.java:332)
>>> at 
>>> hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
>>> 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)
>>> ... 1 more
>>>
>>> Using the dockerfile closure, it's unclear if args is for the build 
>>> command or the subsequent run command (my guess is the latter).
>>> 

Re: Jenkins node selection

2017-02-07 Thread David Karr
On Tuesday, February 7, 2017 at 12:36:59 PM UTC-8, Tejinder Kaur Gill wrote:
>
> How can we specify the node on which Jenkins multibranch pipeline job will 
> run,by default it run on master nd creating space issue on master ,need to 
> configure on some slave .
>

I'm frankly not certain about multibranch vs. "plain" pipeline, but in an 
ordinary pipeline script, you can pass a "label" to the node function, so 
instead of this:
node {
   ...
}

 You can do (for instance):
node("docker") {
 ...
}

By default, this will reference a node with that name, but you really 
should add "labels" to your slave definitions, expressing the kinds of 
functionality that slave can handle.  If there's one particular slave that 
should be used for docker builds, then put that label value on it.

-- 
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/5903e94d-5a48-4fea-b812-d0197bd60ef8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Issue with pipeline

2017-02-07 Thread David Karr
On Tuesday, February 7, 2017 at 10:15:06 AM UTC-8, Sharan Basappa wrote:
>
> Hi All,
>
> I am having some trouble executing basic shell commands (highlighted in 
> red). I cant figure out the issue. Need some help. This is what I get:
>
> Branch indexing
>
> > git rev-parse --is-inside-work-tree # timeout=10
>
> Setting origin to git@hd1:testing
>
> > git config remote.origin.url git@hd1:testing # timeout=10
>
> Fetching origin...
>
> Fetching upstream changes from origin
>
> > git --version # timeout=10
>
> > git fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/*
>
> Seen branch in repository origin/master
>
> Seen branch in repository origin/test
>
> Seen branch in repository origin/test1
>
> Seen branch in repository origin/testx
>
> Seen 4 remote branches
>
> > 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/*
>
> Checking out Revision eb966a50720c888113925000ad9179c79b1c187b (test1)
>
> > git config core.sparsecheckout # timeout=10
>
> > git checkout -f eb966a50720c888113925000ad9179c79b1c187b
>
> > git rev-list eb966a50720c888113925000ad9179c79b1c187b # timeout=10
>
> [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/an_example_test1-24PKZ6E7JM3ZFPAWUPX5ZXTQQLVB7HDDUSAFFRMP6IX3XZERQFTA
>
> [Pipeline] {
>
> [Pipeline] sh
>
> [an_example_test1-24PKZ6E7JM3ZFPAWUPX5ZXTQQLVB7HDDUSAFFRMP6IX3XZERQFTA] 
> Running shell script
>
> + pwd
>
>
> /var/lib/jenkins/workspace/an_example_test1-24PKZ6E7JM3ZFPAWUPX5ZXTQQLVB7HDDUSAFFRMP6IX3XZERQFTA
>
> [Pipeline] sh
>
> [an_example_test1-24PKZ6E7JM3ZFPAWUPX5ZXTQQLVB7HDDUSAFFRMP6IX3XZERQFTA] 
> Running shell script
>
> + cat simple.csh
>
> *cat: simple.csh: No such file or directory*
>

When I run into issues like this, I often will run "sh('pwd')" and 
"sh('ls')" in the script, to verify exactly where I think I am, and what 
else is in the directory. The output from those should help.
 

> [Pipeline] }
>
> [Pipeline] // node
>
> [Pipeline] End of Pipeline
>
> ERROR: script returned exit code 1
>
> 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/7b73b757-c8d5-42eb-b047-a269aa15abd1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Size of build in trends

2017-02-07 Thread Tejinder Kaur Gill
Can we get the size of build generated in trends in pipeline job
?

-- 
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/20193a52-66b2-4b2b-aa59-7bad113b9dac%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Jenkins node selection

2017-02-07 Thread Tejinder Kaur Gill
How can we specify the node on which Jenkins multibranch pipeline job will 
run,by default it run on master nd creating space issue on master ,need to 
configure on some slave .

-- 
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/8fb9b7b9-3974-48aa-a1eb-92f9823f561c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Is there any way to get Jenkins to tell me about actual compile errors instead of just failing with an anonymous error?

2017-02-07 Thread David Karr
Today I've been iterating on changes in a shared library, and I find it 
very frustrating that trivial compile errors in the library source just 
result in "ErrorCollector" stacktraces, with no useful information.  For 
instance, I had some iterations that failed because I was missing an import 
statement for a class I was referencing.  I simply added the import for the 
missing class, and the error went away.  However, I had to realize what 
class I was missing the import for.  I've managed to get Eclipse to tell me 
when I have basic Groovy syntax errors, but it doesn't tell me if I'm 
missing an import for a referenced class.

-- 
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/9ebe8956-4240-4449-a9c8-c00d203035f3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Build periodically with Parameters support

2017-02-07 Thread Indra Gunawan (ingunawa)
Please check the plugin’s Github project;  there are PR for pipeline support 
that have yet been accepted :
https://github.com/jenkinsci/parameterized-scheduler-plugin/pulls

In short, it is not compatible with pipeline.


From:  on behalf of Sreeram Krishna 

Reply-To: "jenkinsci-users@googlegroups.com" 
Date: Tuesday, February 7, 2017 at 9:26 AM
To: "jenkinsci-users@googlegroups.com" 
Subject: Re: Build periodically with Parameters support

Its this one: 
https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Scheduler+Plugin

On Mon, Feb 6, 2017 at 11:15 PM, Daniel Beck 
> wrote:
It's unclear what plugin you're referring to.

> On 06.02.2017, at 23:05, Sam K 
> > wrote:
>
> Anyone?
>
> On Thursday, February 2, 2017 at 3:41:47 PM UTC-8, Sam K wrote:
> I could not find this plugin in the compatibility page here: 
> https://github.com/jenkinsci/pipeline-plugin/blob/master/COMPATIBILITY.md
>
> Is there a way I can schedule the same job with different parameters?  I am 
> using a non-declarative job just to kick off my parameterized declarative 
> pipeline each night.  :)
>
>
> --
> 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/e7a1b576-1b52-4599-8ab4-cecd04919f44%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the Google 
Groups "Jenkins Users" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/jenkinsci-users/Ep8vEMkBYdw/unsubscribe.
To unsubscribe from this group and all its topics, 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/3AB19AFD-7430-42A0-A974-384DC372C7BB%40beckweb.net.
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/CAKn1gMvrF3mjDZbObd_Js2D0CLj22mXcB50QHZ0AufUv3VJ-1Q%40mail.gmail.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/FBC46C1F-72A1-40D8-8704-DD28D9383925%40cisco.com.
For more options, visit https://groups.google.com/d/optout.


Re: Issue with pipeline

2017-02-07 Thread Indra Gunawan (ingunawa)
Do you have the simple.csh file checked-in or not?


From:  on behalf of Sharan Basappa 

Reply-To: "jenkinsci-users@googlegroups.com" 
Date: Tuesday, February 7, 2017 at 10:15 AM
To: Jenkins Users 
Subject: Issue with pipeline

Hi All,

I am having some trouble executing basic shell commands (highlighted in red). I 
cant figure out the issue. Need some help. This is what I get:


Branch indexing

> git rev-parse --is-inside-work-tree # timeout=10

Setting origin to git@hd1:testing

> git config remote.origin.url git@hd1:testing # timeout=10

Fetching origin...

Fetching upstream changes from origin

> git --version # timeout=10

> git fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/*

Seen branch in repository origin/master

Seen branch in repository origin/test

Seen branch in repository origin/test1

Seen branch in repository origin/testx

Seen 4 remote branches

> 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/*

Checking out Revision eb966a50720c888113925000ad9179c79b1c187b (test1)

> git config core.sparsecheckout # timeout=10

> git checkout -f eb966a50720c888113925000ad9179c79b1c187b

> git rev-list eb966a50720c888113925000ad9179c79b1c187b # timeout=10

[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/an_example_test1-24PKZ6E7JM3ZFPAWUPX5ZXTQQLVB7HDDUSAFFRMP6IX3XZERQFTA

[Pipeline] {

[Pipeline] sh

[an_example_test1-24PKZ6E7JM3ZFPAWUPX5ZXTQQLVB7HDDUSAFFRMP6IX3XZERQFTA] Running 
shell script

+ pwd

/var/lib/jenkins/workspace/an_example_test1-24PKZ6E7JM3ZFPAWUPX5ZXTQQLVB7HDDUSAFFRMP6IX3XZERQFTA

[Pipeline] sh

[an_example_test1-24PKZ6E7JM3ZFPAWUPX5ZXTQQLVB7HDDUSAFFRMP6IX3XZERQFTA] Running 
shell script

+ cat simple.csh

cat: simple.csh: No such file or directory

[Pipeline] }

[Pipeline] // node

[Pipeline] End of Pipeline

ERROR: script returned exit code 1

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/73d02186-75a9-4e8a-8787-5ca05cc38ba5%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/921C54C2-9941-47E8-B320-1B6796C00F8A%40cisco.com.
For more options, visit https://groups.google.com/d/optout.


Issue with pipeline

2017-02-07 Thread Sharan Basappa
Hi All,

I am having some trouble executing basic shell commands (highlighted in 
red). I cant figure out the issue. Need some help. This is what I get:

Branch indexing

> git rev-parse --is-inside-work-tree # timeout=10

Setting origin to git@hd1:testing

> git config remote.origin.url git@hd1:testing # timeout=10

Fetching origin...

Fetching upstream changes from origin

> git --version # timeout=10

> git fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/*

Seen branch in repository origin/master

Seen branch in repository origin/test

Seen branch in repository origin/test1

Seen branch in repository origin/testx

Seen 4 remote branches

> 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/*

Checking out Revision eb966a50720c888113925000ad9179c79b1c187b (test1)

> git config core.sparsecheckout # timeout=10

> git checkout -f eb966a50720c888113925000ad9179c79b1c187b

> git rev-list eb966a50720c888113925000ad9179c79b1c187b # timeout=10

[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/an_example_test1-24PKZ6E7JM3ZFPAWUPX5ZXTQQLVB7HDDUSAFFRMP6IX3XZERQFTA

[Pipeline] {

[Pipeline] sh

[an_example_test1-24PKZ6E7JM3ZFPAWUPX5ZXTQQLVB7HDDUSAFFRMP6IX3XZERQFTA] 
Running shell script

+ pwd

/var/lib/jenkins/workspace/an_example_test1-24PKZ6E7JM3ZFPAWUPX5ZXTQQLVB7HDDUSAFFRMP6IX3XZERQFTA

[Pipeline] sh

[an_example_test1-24PKZ6E7JM3ZFPAWUPX5ZXTQQLVB7HDDUSAFFRMP6IX3XZERQFTA] 
Running shell script

+ cat simple.csh

*cat: simple.csh: No such file or directory*

[Pipeline] }

[Pipeline] // node

[Pipeline] End of Pipeline

ERROR: script returned exit code 1

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/73d02186-75a9-4e8a-8787-5ca05cc38ba5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Build periodically with Parameters support

2017-02-07 Thread Sreeram Krishna
Its this one:
https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Scheduler+Plugin

On Mon, Feb 6, 2017 at 11:15 PM, Daniel Beck  wrote:

> It's unclear what plugin you're referring to.
>
> > On 06.02.2017, at 23:05, Sam K  wrote:
> >
> > Anyone?
> >
> > On Thursday, February 2, 2017 at 3:41:47 PM UTC-8, Sam K wrote:
> > I could not find this plugin in the compatibility page here:
> https://github.com/jenkinsci/pipeline-plugin/blob/master/COMPATIBILITY.md
> >
> > Is there a way I can schedule the same job with different parameters?  I
> am using a non-declarative job just to kick off my parameterized
> declarative pipeline each night.  :)
> >
> >
> > --
> > 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/e7a1b576-1b52-4599-8ab4-cecd04919f44%40googlegroups.
> com.
> > For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/jenkinsci-users/Ep8vEMkBYdw/unsubscribe.
> To unsubscribe from this group and all its topics, 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/3AB19AFD-7430-42A0-A974-384DC372C7BB%40beckweb.net.
> 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/CAKn1gMvrF3mjDZbObd_Js2D0CLj22mXcB50QHZ0AufUv3VJ-1Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Jenkins git supports subtree?

2017-02-07 Thread Witold Konior
Hi,

I have exactly same problem. I have some subtree folder I want to update 
with every build.

Please let me know if there is any proper solution for that with pipeline 
configuration.

Best regards,
Witold

-- 
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/8d715d0a-b3a3-499e-8807-b64fd1f4240c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


How to search jenkins artifacts copied from one job to another.

2017-02-07 Thread Moshe Zuisman
Hi.
I have 2 jenkins jobs(both runs on amazon EC2 nodes).
One archive some file as artifact. Second is defined to have an access to 
those artifact.
When I comes to second node (that access artifact, created by first one) I 
see that those artifact lays under directorry :
*workspace\label=windows2012Aws_ONE_LOCAL_MSSQL*
Where *windows2012Aws_ONE_LOCAL_MSSQL *is name of primary job - that 
creates artifact...
Is there some Jenkins mnemonic, that I can put in my second job - to point 
my script (power-shell) where ios those file located? Or I have to use 
hardcoded path %workspace%../../../*label=windows2012Aws_ONE_LOCAL_MSSQL *like 
I have to do now?

-- 
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/099cae7f-9656-47e8-8986-6327016ec4a4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


buildInfoxxxx.properties on /tmp directory on Jenkins server exposing the credentials

2017-02-07 Thread Makarand Jadhav
Hi,

We have been using gradle build tool(Gradle Plugin) for compiling the 
source code and then using the Artifactory plugin(Gradle-Artifactory 
Integration) for publishing the artifacts to the Artifactory server from 
the Jenkins server. 
Our server administrator reported that there are lot of 
buildInfo.properties on /tmp directory(where  is any arbitrary 
number generated by build) on Jenkins server and its been observed that 
contents of buildInfo.properties are exposing the credentials of some 
of the resources accessed during the build & deploy process(e.g.: 
credentials of Artifactory, DB, Shared drives etc.). The excerpt of 
contents of buildInfo.properties(many lines deleted & masked) is as 
below:
--
artifactory.publish.contextUrl=
artifactory.publish.ivy.m2compatible=
buildInfo.env.JenkinsScripts=
buildInfo.env.APP_DB_USER=
artifactory.publish.record.all.dependencies=
buildInfo.env.JOB_NAME=
artifactory.resolve.password=X
-

Since this is an delivery pipeline configured, we use "Environment 
Injector" & the "Mask Passwords" plugin which masks the password in the 
Jenkins UI console logs but not sure why the credentials are exposed and 
readable in the buildInfo.properties file.

So I have two questions:

   1. Is there any way that we can mask the information for credentials in 
   the buildInfo.properties file?
   2. Can the build automatically cleanup the buildInfo.properties 
   after the build completes as there are lots of files being leftover in the 
   /tmp directory filling up the disk space and are cleaned up through an 
   automated script?

 Any suggestions/comments are greatly 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/ab3d82f1-354e-4d0b-b259-6dae847c0261%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: How To Trigger a build throgh Jenkins when a change is pushed to GitLab

2017-02-07 Thread Allen Geer
https://wiki.jenkins-ci.org/display/JENKINS/Gitlab+Hook+Plugin

Did you try this?

On Tuesday, February 7, 2017 at 3:51:54 AM UTC-7, Sivakrishna Yarra wrote:
>
> Hello Team,
> How can i trigger a build automatically when a changed is pushed to GitLab 
> Private Project. 
>

-- 
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/e87a3be3-c531-4b0b-b59e-031b2e05ae21%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


How To Trigger a build throgh Jenkins when a change is pushed to GitLab

2017-02-07 Thread Sivakrishna Yarra
Hello Team,
How can i trigger a build automatically when a changed is pushed to GitLab 
Private Project. 

-- 
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/431ccbdc-5ea7-415b-903c-0463f520a5ce%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Trigger a parameterized build with file parameter from C#

2017-02-07 Thread Oli Spicer
Hi,

I have a parameterized build which takes a file parameter. Its goal is to 
simply upload a file to the jenkins server.

I need to trigger this job, and upload the file, via C# code.  I've tried 
different methods, but I either get an 500 Internal Server error or a 403 
Forbidden error, although my credentials are correct.

On the remote access API page all they give is this curl command :

curl -X POST JENKINS_URL/job/JOB_NAME/build \
  --user USER:PASSWORD \
  --form file0=@PATH_TO_FILE \
  --form json='{"parameter": [{"name":"FILE_LOCATION_AS_SET_IN_JENKINS", 
"file":"file0"}]}'


>From what I understand, I need to make a POST request as a 
>"multipart/form-data" content type and put the contents of the file in the 
>request body.


Does anyone know how to trigger this kind of job from a C# program ?


Thank you,


Oli

-- 
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/fc541711-8322-446d-990b-f0d902263848%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.