Documentation:
https://github.com/jenkinsci/workflow-plugin/blob/master/scm-step/README.md#polling
> On 21.12.2015, at 17:05, Mark Bidewell wrote:
>
> I am considering Workflows to automate build and release. Can a workflow be
> called in a CI polling manner? There is a
> On 21.12.2015, at 10:19, Max Kovgan wrote:
>
> After setting it to: IP:EXT_PORT, everything started working.
Weird, we should already support both cases (i.e. separate and combined
host/port). Maybe you could take a look at this and compare to your setup?
> On 21.12.2015, at 04:58, Swiveling Raveesh wrote:
>
> I guess that would make sense that it just redirects back to the SSO page.
> But right now a logged in user cannot sign out at all. So once you are logged
> in there is no way to authenticate with a different
We use the gradle/groovy dsl to create our jenkins jobs.
We have a need to have parameterized jenkins jobs which create
job-sets+views to avoid various folks needing to run gradle scripts/pass
parameters in order to create job sets. For example a job set might
retrieve source from a specific
> On 21.12.2015, at 23:00, Joe Ferr wrote:
>
> much cleaner if the current logged in user's api token was somehow exposed
> (as an env var?)/ made available to my gradle script.
And by "cleaner" you mean "enable your users to steal other users' API tokens
just because
> On 11.12.2015, at 16:17, Ivan Hamer wrote:
>
> I run Jenkins v1.640, and on about 10% of aborts (either manual or through
> timeout plugin), Jenkins server exits with the attached output.
To clarify, the Jenkins master exits, and afterwards is not running anymore?
--
You
To Max,
Would you mind sharing your nginx jenkins con file? I have followed many
URL on internet about proxy Jenkins with nginx but I am never able to make
the ³Warning Šyour proxy is broken ..² to disappear.
Thank you
-Indra
On 12/21/15, 10:39 AM, "jenkinsci-users@googlegroups.com on behalf
I'd use the Mask Password plugin to hide the exposed token from the console
output so I don't think there would be a way to steal others users API
tokens.
A password parameter would work but it means that they need to login
twice...Not really a big deal; they've already logged into Jenkins. I
Hi, Daniel!
Thanks, for the direction.
whatever you've suggested, I ran:
import hudson.model.*
import jenkins.model.*
import org.kohsuke.stapler.*
println
org.kohsuke.stapler.Stapler.getCurrentRequest().getHeader('X-Forwarded-Port')
println Jenkins.instance.rootUrlFromRequest
The output was:
Greetings all.
After upgrading from 1.596.2 LTS to 1.625.3 LTS, all my jobs are showing
"Dec 31, 1969" as the build date in the build history.
It appears the reason is that Jenkins has switched from using a
date/time-based directory in "builds" to a simple number-based directory,
but even
Hi,
2.24.1 doesn't break up promotions.
Thank you for your help.
On Saturday, 19 December 2015 19:28:13 UTC+1, Victor Martinez wrote:
>
> Hi,
>
> I've seen in the release notes a new version 2.24.1 which does revert a
> particular PR:
Ah that makes sense. I didn't consider it just re-signing in. I was
expecting to see an account selection screen from google.
On Mon, Dec 21, 2015 at 1:41 PM, Daniel Beck wrote:
>
> > On 21.12.2015, at 04:58, Swiveling Raveesh
> wrote:
> >
> > I guess
Hello,
These tables are coming from the plugins that *our organization have
developed *.The alignment was coming properly* one above the other* in
jenkins 1.580.3 ..but i find alignment issue in jenkins 1.625.2...
Thanks,
Shakir Ali.
On Thursday, December 17, 2015 at 5:53:02 PM
I managed to fix the issue: the value of header "Host" contained only IP.
After setting it to: IP:EXT_PORT, everything started working.
I'll post this to wiki later on.
Regards!
On Dec 21, 2015 10:51, "Max Kovgan" wrote:
> Hi, Daniel!
> Thanks, for the direction.
> whatever
Hi,
Ah ok. There were many changes to the UI since that time. You're very
likely to have to have to adapt your code then.
Cheers
Le 21 déc. 2015 10:45 AM, "Shakir Ali" a écrit :
> Hello,
> These tables are coming from the plugins that *our organization have
> developed
I had the same issue with OpenJDK 1.7.0 on CentOS 6.5. Upgrading to nss
3.19 fixed the issue.
Thanks for the inputs everyone. Thanks Lukasz.
On Tuesday, October 27, 2015 at 7:50:02 PM UTC+5:30, Łukasz Korzybski wrote:
>
>
> I had the same issue with OpenJDK 1.7.0 on CentOS 6.6. I had nss 3.16
I believe that if you pass "poll: true" to the "scm" step, it'll use that
particular scm config for polling.
A.
On Mon, Dec 21, 2015 at 11:05 AM, Mark Bidewell wrote:
> I am considering Workflows to automate build and release. Can a workflow
> be called in a CI polling
I am considering Workflows to automate build and release. Can a workflow
be called in a CI polling manner? There is a "Poll SCM" build trigger but
nowhere to input SCM details.
What I would like to do is the following:
1) On SCM change execute a CI build.
2) Between stages prompt for
18 matches
Mail list logo