for my use case, we only care about PR build. I ended up to setup jenkins
file to let branch builds pass thru ( ie always green). and it is an on
going confusion
Thanks
-Dan
On Tuesday, May 2, 2017 at 9:20:46 PM UTC-7, Kevin Burnett wrote:
>
> i'm actually totally with you on this.
>
> i've
I'm assuming that not all of us have been added in to help the effort as I
can't personally see any management functions...
Richard.
On Tue, 2 May 2017 at 08:50 Arnaud Héritier wrote:
> Did you add all of us as moderators Tyler ?
>
> On Sun, Apr 30, 2017 at 1:44 PM, Mark Waite
> wrote:
>
>> I
The File constructor is blacklisted so that users don't try to do the
mistake that you are doing.
The pipeline code is running on the master (only the steps themselves are
actually running on the agent), so when you create a new file pointing it
to $workspace it is most likely not there on the m
Hi Mark,
thanks for your reply.
I filed a bug for it (https://issues.jenkins-ci.org/browse/JENKINS-44018)
Cheers,
Jaap
Op dinsdag 2 mei 2017 14:30:39 UTC+2 schreef Mark Waite:
>
> I think you've detected a bug (or likely multiple bugs). I think they may
> be due to the recent updates to the tril
I can disable CSP from the script console with this
System.setProperty("hudson.model.DirectoryBrowserSupport.CSP", "")
what is the correct syntax for setting this a jenkins start time on Ubuntu
*-Dhudson.model.DirectoryBrowserSupport.CSP=\"\**" *
*-Dhudson.model.DirectoryBrowserSupport.CSP="**"
Thanks a lot Robert, that solved my problem. You are right, i should not
whitelist those methods just load properties fille. Your plugin seems to be
great, i will invest some time in learning other methods as well.
Also, do you think i can load the properties outside of a stage somehow ? I
hate
Hi,
I'm in the process of doing dry run upgrades on a VM Jenkins cluster in
preparation for upgrading my employer's production cluster. The current
version on the master 1.609.3 and I'm trying to upgrade to 2.46.2 LTS. For
reasons outside of my control, we run under Tomcat and I have already
Found solution here: https://issues.jenkins-ci.org/browse/JENKINS-43393
Revert maven-integration plugin to 2.14
--
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
Hello,
I premit I'm quite new to jenkins and to pipeline in particular.
I've a web application that's composed of a main application and several
modules.
My jenkins pipeline is the following
node
{
def libName = "Project"
def slnPath = "F:\\Build\\Jenkins\\jobs\\Project\\workspac
Hello,
I'm getting the following error pretty frequently (~25% of the time) when
starting pipeline jobs on one of our Jenkins servers. It occurs in the scm
step of our pipelines, and I've seen it in all 3 of our pipelines on this
server:
Failed to parse
/opt/jenkins/inst/jobs/nightly.build/b
I am using declarative syntax to build my pipeline. I am loading several
variables from a properties file in the beginning and i now i would like to
control the 'on which slave node something executes' via variables. But i
cannot figure out how to use variable as a agent label. The following is
I am using declarative pipeline and in some of my stages, i need to use
multiple agents while still ensuring the steps are executed in sequence
(not parallel). I don't find a nice way to use multiple agents (maybe
multiple steps) within a stage.
something like:
pipeline {
agent none
Summarizing this and adding a little information. We still don't have a
solution.
We're still getting "It appears that your reverse proxy set up is broken."
on the Manage Jenkins page.
Jenkins 2.46.2 .war file
Tomcat 8.5.14.
Windows Server 2012 R2 Datacenter 64-bit
IIS 8.5
Java 1.8.0_131 6
I've gotten similar requests before to have some type of similar
behavior/mode as readTrusted, so maybe it gets implemented sometime in the
future.
/B
On Wed, May 3, 2017 at 2:38 PM, ishan jain wrote:
> Thanks a lot Robert, that solved my problem. You are right, i should not
> whitelist those m
It should work if you use double quotes around your agent variable.
Variable resolution will not happen within single quotes.
On 5/3/2017 10:58 AM, ishan jain wrote:
I am using declarative syntax to build my pipeline. I am loading
several variables from a properties file in the beginning and i
On 3 May 2017 at 16:30, Terry Lacy wrote:
> /administrativeMonitor/hudson.diagnosis.ReverseProxySetupMonitor/
> testForReverseProxySetup/https:/our.server.name/manage/
>
That looks to be the malformed url. you should want to see why it is
converting the URL to "https:/our.server.name" and not "
Hi, Stephen,
Thanks for your reply. I don't have any ideas on why it would be converting
the URL that way. Could be an URL encoding issue, but I have no idea how
to fix it.
Terry
On Wednesday, May 3, 2017 at 10:39:04 AM UTC-6, Stephen Connolly wrote:
>
>
> On 3 May 2017 at 16:30, Terry Lacy >
For whatever it's worth, adding another "/" to that URL still results in a
404.
Terry
On Wednesday, May 3, 2017 at 10:39:04 AM UTC-6, Stephen Connolly wrote:
>
>
> On 3 May 2017 at 16:30, Terry Lacy >
> wrote:
>
>>
>> /administrativeMonitor/hudson.diagnosis.ReverseProxySetupMonitor/testForRever
Is there an ip v6 enabled as well?
On Mon, May 1, 2017 at 1:16 PM Terry Lacy wrote:
> I'm not sure if this is useful information, but we see this in the
> jenkins-stderr logs when browsing to the Manage Jenkins page:
>
> 01-May-2017 12:10:39.038 WARNING [Handling GET
> /administrativeMonitor/hu
Does this means that your reverse proxy is not working?
And not just the error on the jenkins page
On Wed, May 3, 2017 at 12:28 PM Terry Lacy wrote:
> For whatever it's worth, adding another "/" to that URL still results in a
> 404.
>
> Terry
>
> On Wednesday, May 3, 2017 at 10:39:04 AM UTC-6, S
I wondered about that too. I'll get with our SA and see. I wonder whether
it'd be better to use "127.0.0.1" in the configuration instead of
"localhost"
On Wednesday, May 3, 2017 at 11:28:34 AM UTC-6, ok999 wrote:
>
> Is there an ip v6 enabled as well?
>
>
> On Mon, May 1, 2017 at 1:16 PM Terry
By all appearances, the reverse proxy is working. However, we haven't done
really extensive testing yet. I've just done a couple of builds and tested
with one slave.
So, yeah, so far, it's just the message on the Jenkins Manage Jenkins page.
However, I'm assuming the message is there for a rea
Okay, we verified that ipv6 was disabled on the network interface. We also
changed the IIS reverse proxy to point to "127.0.0.1:8080" instead of
"localhost:8080". That didn't make any difference.
On Wednesday, May 3, 2017 at 11:28:34 AM UTC-6, Terry Lacy wrote:
>
> For whatever it's worth, addin
Jenkins 2.51, running on Windows 7.
We've made very little changes for awhile (configuration, jobs, etc) but we
did recently upgrade it from several versions back. And I added the
Capitomcat and Deploy to container plugins (which brought in some of their
dependencies).
I created a couple freestyl
Hi James,
We figured out the cause of the failure, will be released today some time.
And also regarding the JIRA component issue, we raised request to create
component for this plugin. Soon this also will be created.
Thanks for raising the issue.
-Suresh
On Friday, April 28, 2017 at 10:41:51 PM
Hi James,
Fix has been released in 1.6 version.
-Suresh
On Friday, April 28, 2017 at 10:41:51 PM UTC+5:30, James Green wrote:
>
> This plugin works fine downloading binaries from various web sites, but
> give it a file to download from Nexus and it fails instantly with no error:
>
> [Pipeline] s
26 matches
Mail list logo
