date:20170824

Re: Moving From Parameterized Trigger Plugin to Pipelines

2017-08-24 Thread Michael Pailloncy

Hello,

To load a properties file, you can install this plugin :
https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Utility+Steps+Plugin
Then, you will have access to *readProperties* utility step. See
https://github.com/jenkinsci/pipeline-utility-steps-plugin/blob/master/docs/STEPS.md
for usage

IIUC your case, it will be worthwhile to create a method translating
properties to build parameters.

Moreover, for maintenance easiness, the best is to create Shared Libraries
 to declare common
steps for all yours pipelines in a centralized way.

My 2 cents

2017-08-24 21:43 GMT+02:00 AJ Ferrigno :

> Hello,
>
> I am trying to move towards Pipelines instead of our Build Flow /
> Parameterized Trigger plugin setup. It is mostly making sense, but there is
> one thing that seems very cumbersome / maybe even impossible under
> Pipelines which I can do with ease via the Parameterized Trigger plugin
> (see documentation here
> ).
>
> I like the concept of being able to trigger another job, and specify a
> properties file (each line is in the format x=y) somewhere in my job's
> workspace which automatically become the parameters of the next job in the
> sequence. It would be awesome to have this functionality exist somewhere in
> Pipelines as a step or some one-liner I could use.
>
> For example, say I have this pipeline (basically: create parameters for a
> deploy, then deploy using those parameters):
>
>>
>> pipeline {
>> agent any
>>
>> stages {
>> stage('Parameters') {
>>  steps {
>> build job: "DeployParameters", parameters: [string(name:
>> 'project', value: project), string(name: 'branchName', value: branchName)]
>> /* grab artifact file "artifact.txt" from
>> "DeployParameters" job and set a bunch of variables based on it */
>> }
>> }
>> stage('Deploy') {
>>  steps {
>> build job: "DeployJob", parameters: /* pass in all
>> parameters set above */
>>  }
>
>
> First of all, looking at the commented lines, is the above possible at
> all, using a step or otherwise? I tried using the below code to do
> something similar, but it (Jenkins v2.74) complained "Scripts not permitted
> to use new java.util.Properties"
>
> step([$class: 'CopyArtifact',
>>  filter: 'artifact.txt',
>>  projectName: "DeployParameters"])
>> script {
>>  def content = readFile 'artifact.txt'
>>  Properties properties = new Properties()
>>  InputStream is = new ByteArrayInputStream(content.getBytes());
>>  properties.load(is)
>>  def runtimeString = 'variable_i_want'
>>  variable_i_want = properties."$runtimeString" }
>
>
> I know I can probably tell my Jenkins installation to allow
> java.util.Properties, but that seems like an unsustainable hack. I don't
> think I'm doing anything terribly insecure here, so I would really like to
> be above-board about it.
>
> Second, even if I could get the above code to work, it is simply too long
> and un-maintainable. Especially since I would probably be re-using this
> many times, it would be awesome to replace this functionality in the
> Parameterized Trigger plugin with a simple one-liner. It may even help
> somebody else somewhere.
>
> Has anybody else needed something like this? If this is a feature request
> not currently thought of, what would it take to get this solution developed?
>
> Thanks for any help,
> AJ
>
> --
> 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/CAKzFqnPUNHyZOjQztGKkTKuA7d27o
> Ygj0AqgHfh94Ehs6E6Rug%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/CAPO77c1FYk93e37Lr7o7sheP2kG%3DvYFEa903_tJgJEnEFzg36Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Moving From Parameterized Trigger Plugin to Pipelines

2017-08-24 Thread AJ Ferrigno

Hello,

I am trying to move towards Pipelines instead of our Build Flow /
Parameterized Trigger plugin setup. It is mostly making sense, but there is
one thing that seems very cumbersome / maybe even impossible under
Pipelines which I can do with ease via the Parameterized Trigger plugin
(see documentation here
).

I like the concept of being able to trigger another job, and specify a
properties file (each line is in the format x=y) somewhere in my job's
workspace which automatically become the parameters of the next job in the
sequence. It would be awesome to have this functionality exist somewhere in
Pipelines as a step or some one-liner I could use.

For example, say I have this pipeline (basically: create parameters for a
deploy, then deploy using those parameters):

>
> pipeline {
> agent any
>
> stages {
> stage('Parameters') {
>  steps {
> build job: "DeployParameters", parameters: [string(name:
> 'project', value: project), string(name: 'branchName', value: branchName)]
> /* grab artifact file "artifact.txt" from
> "DeployParameters" job and set a bunch of variables based on it */
> }
> }
> stage('Deploy') {
>  steps {
> build job: "DeployJob", parameters: /* pass in all
> parameters set above */
>  }


First of all, looking at the commented lines, is the above possible at all,
using a step or otherwise? I tried using the below code to do something
similar, but it (Jenkins v2.74) complained "Scripts not permitted to use
new java.util.Properties"

step([$class: 'CopyArtifact',
>  filter: 'artifact.txt',
>  projectName: "DeployParameters"])
> script {
>  def content = readFile 'artifact.txt'
>  Properties properties = new Properties()
>  InputStream is = new ByteArrayInputStream(content.getBytes());
>  properties.load(is)
>  def runtimeString = 'variable_i_want'
>  variable_i_want = properties."$runtimeString" }


I know I can probably tell my Jenkins installation to allow
java.util.Properties, but that seems like an unsustainable hack. I don't
think I'm doing anything terribly insecure here, so I would really like to
be above-board about it.

Second, even if I could get the above code to work, it is simply too long
and un-maintainable. Especially since I would probably be re-using this
many times, it would be awesome to replace this functionality in the
Parameterized Trigger plugin with a simple one-liner. It may even help
somebody else somewhere.

Has anybody else needed something like this? If this is a feature request
not currently thought of, what would it take to get this solution developed?

Thanks for any help,
AJ

-- 
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/CAKzFqnPUNHyZOjQztGKkTKuA7d27oYgj0AqgHfh94Ehs6E6Rug%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

MSTest plugin poll

2017-08-24 Thread Ivo Bellin Salarin

Hello everyone,

I have implemented a couple of blueprints (i.e. modification requests) of
the MSTest plugin for Jenkins. Since I haven't any other way to contact my
users, I will try to use this mailing list to describe the changes and have
your opinion.

First, the possibility to use the MSTest plugin in a pipeline
(jenkinsfile). The users will be able to call the plugin using the 'mstest'
symbol.

Second. Because of the changes apported to implement the pipeline, and
because of several users request, I have dropped the dependency upon the
Emma plugin. Versions 0.12 through 0.19 were showing coverage trends (or a
bad looking picture if the tests weren't computing any coverage). These
versions were 1) discovering code coverage reports linked by the test
report 2) converting it to the Emma format 3) adding a Emma report to the
build.
Starting from the 0.20 version, the plugin will perform the steps 1 and 2,
but it won't do the step 3. In order to show the coverage report/trends,
you will have to add the Emma plugin (or the jacoco plugin) and tell it to
find for the reports whose name matches '**/emma/coverage.xml'.

Dear users, what do you think about these changes? I will wait 2 weeks
before releasing the 0.20 version.

BTW, someone has tested the 0.20 version, but only partially. I have
executed all the unit tests in my possession (and I have written some more
for the occasion). But the number of TRX/coverage reports in my possession
is very limited. So, if anybody can help testing the 0.20 version, please
send me a private message.

Many thanks for your attention,
Have a great day,
Ivo

--
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/CAPc4eF9-a4b5f4Bd%2BiAHThaVr46xqOF5GrmPKxWRwwjCbY4ttw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Still trying to fix "It appears that your reverse proxy set up is broken" with IIS 8.5

2017-08-24 Thread Terry Lacy

We still have no solution for this. 

See https://groups.google.com/d/msg/jenkinsci-users/wmhprlRiVmI/7q4Il_xRBgAJ 
for more details.

Does anyone have a working IIS 8.5 web.config that doesn't give "your 
reverse proxy set up is broken"?

Terry

-- 
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/1bddd8d2-994f-45db-ae7e-a7fd11e24b1d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Kubernetes Plugin

2017-08-24 Thread Carlos Sanchez

I've seen it reported before.
Check your pod logs, events and exit codes

On Thu, Aug 24, 2017 at 6:35 PM, Pedro Januário 
wrote:

> Hi,
>
> I am using Jenkins Pipeline with Kubernetes Plugin and doing something
> really simple just to build a container and run the container to execute
> the tests on it.
>
> While doing it I got a error that shows exit -2 without another
> information, currently I am just doing a echo.
>
> *Example (just part of it):*
>
> def containersForUnitTest = [
>   containerTemplate(name: 'mongotest',
>   image: 'mongo:3.2.4',
>   ttyEnabled: true, command: 'mongod --smallfiles',
>   resourceLimitCpu: '150m',
>   resourceRequestCpu: '100m',
>   resourceRequestMemory: '512Mi',
>   resourceLimitMemory: '512Mi',
>   alwaysPullImage: false),
>   containerTemplate(name: 'microservice',
>   image: "..myimage...",
>   ttyEnabled: true, command: 'cat',
>   resourceLimitCpu: '150m',
>   resourceRequestCpu: '100m',
>   resourceRequestMemory: '512Mi',
>   resourceLimitMemory: '512Mi')
> ]
>
> podTemplate(name: "test", inheritFrom: 'jnlp', label: test", containers:
> containersForUnitTest) {
>   node("some") {
> stage('Test') {
>   try {
> container('microservice') {
>   sh """
>echo "this is my echo thing"
>   """
> }
>   }
>   catch (Exception e) {
> echo "microservice error: ${e}"
> throw e
>   }
> }
>   }
> }
>
> If I add the following line to my dockerfile it will run successfully,
> this seems a awkward behaviour that seems to be related with permissions on
> the container execution. Don't see any other way to workaround this but it
> seems undesired.
>
> RUN chown node:node $APP_DIR \
>   && echo http://dl-cdn.alpinelinux.org/alpine/edge/community/ >>
> /etc/apk/repositories \
>   && apk --no-cache add shadow && usermod -u 1 node
>
> Any clue? Is there anything that can cause this?
>
> --
> 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/b921176c-33ca-48c2-a06e-a673aa6f6e72%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/CALHFn6MuQuzz7N4FSdrhvCEXjoOx5C%3DU3s57%2BmdCM40HNbonag%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Kubernetes Plugin

2017-08-24 Thread Pedro Januário

Hi,

I am using Jenkins Pipeline with Kubernetes Plugin and doing something 
really simple just to build a container and run the container to execute 
the tests on it.

While doing it I got a error that shows exit -2 without another 
information, currently I am just doing a echo.

*Example (just part of it):*

def containersForUnitTest = [
  containerTemplate(name: 'mongotest',
  image: 'mongo:3.2.4',
  ttyEnabled: true, command: 'mongod --smallfiles',
  resourceLimitCpu: '150m',
  resourceRequestCpu: '100m',
  resourceRequestMemory: '512Mi',
  resourceLimitMemory: '512Mi',
  alwaysPullImage: false),
  containerTemplate(name: 'microservice',
  image: "..myimage...",
  ttyEnabled: true, command: 'cat',
  resourceLimitCpu: '150m',
  resourceRequestCpu: '100m',
  resourceRequestMemory: '512Mi',
  resourceLimitMemory: '512Mi')
]

podTemplate(name: "test", inheritFrom: 'jnlp', label: test", containers: 
containersForUnitTest) {
  node("some") {
stage('Test') {
  try {
container('microservice') {
  sh """
   echo "this is my echo thing"
  """
}
  }
  catch (Exception e) {
echo "microservice error: ${e}"
throw e
  }
}
  }
}

If I add the following line to my dockerfile it will run successfully, this 
seems a awkward behaviour that seems to be related with permissions on the 
container execution. Don't see any other way to workaround this but it 
seems undesired.

RUN chown node:node $APP_DIR \
  && echo http://dl-cdn.alpinelinux.org/alpine/edge/community/ >> 
/etc/apk/repositories \
  && apk --no-cache add shadow && usermod -u 1 node

Any clue? Is there anything that can cause this?

-- 
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/b921176c-33ca-48c2-a06e-a673aa6f6e72%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Upgrade Jenkins, or not ?

2017-08-24 Thread Terry O'Leary

I went through a similar situation. We had an older version of Jenkins 
(1.534) on a standalone configuration. I took the approach of standing up a 
new instance of Jenkins, this time with a master/slave configuration. First 
I took inventory of all the plugins that were used on the old Jenkins 
server, and installed them on the new server, and also took not of the 
difference in version to anticipate what issues may arise when setting up 
new jobs. I then used the Job import plugin to pull in all the jobs I had 
on the old Jenkins server to the new server. This made is a lot easier to 
reconfigure the jobs slightly with the new master/slave configuration. 
Aside some minor issues I am working through. the transation wasn't too bad.

The advantages, also mentioned in the other posts are:

   - easier to upgrade Jenkins core with auto upgrade function
   - security updates
   - performance improvements

Terry O

On Wednesday, August 23, 2017 at 4:44:48 PM UTC-4, louwho wrote:
>
> Off and on, I have touched upon Jenkins.  My expertise is InstallShield 
> development, with some Release engineering.  Anyway, new project, taking 
> over the Jenkins build system also.  Current  Jenkins version is 1.609.3, 
> the Jenkins LTS is now 2.6.03.  Putting aside (for now), the old adage of 
> 'if it an't broken, don't fix it', are there any real advantages to 
> upgrading to the latest version, or should I just leave it alone?   The 
> product builds are building PowerBuilder and Java products..and then 
> InstallShield, copies to AWS S3, etc.  We are also considering using some 
> third party tools that will allow us to move the Powerbuilder stuff from 
> the CVS repository to GIT.  As an aside, does anyone know if you can have 
> two versions of PowerBuilder on the same build system?
>

-- 
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/597ea375-c122-4daa-94cd-48fcafd07bf0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: P4 Plugin - Jenkins Poll not triggering builds despite finding changes

2017-08-24 Thread Richard Ginga

Marley. do you want Perforce to checkout those files and perform some kind
of build? if so, then I think $class: 'CheckOnlyImpl' is not what you want.

I doubt its a bug (it could be) but the Perforce support in Jenkins is
pretty robust and has been around for years.

On Wed, Aug 23, 2017 at 5:19 PM, Marley Kudiabor 
wrote:

> When I check the workspace manually I can see that the files are not up to
> date. There are files behind the head revision that match the ones in the
> polling log. I just need to figure out why despite seeing those changes it
> thinks there are no changes.
> Unless this is an actual bug.
>
> On Wednesday, August 23, 2017 at 5:07:51 PM UTC-4, Richard Ginga wrote:
>>
>> the "+" mostly works if you have Quiet turned off.
>>
>> preview check is probably not going to do a build because it has not
>> updated anything in the workspace. It just updated the the workspace's
>> definition on the server to match the current contents of the stream. thus,
>> no changes
>>
>> On Wed, Aug 23, 2017 at 5:03 PM, Marley Kudiabor 
>> wrote:
>>
>>> Additionally I should mention I can't expand the +_ javascript link
>>> below each p4 action. I'm not sure what should be there.
>>>
>>> I'm also using  Preview Check Only
>>>
>>> --
>>> 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-use...@googlegroups.com.
>>> To view this discussion on the web visit https://groups.google.com/d/ms
>>> gid/jenkinsci-users/43779759-ef46-460f-abcd-8b1f86b923a4%
>>> 40googlegroups.com
>>> 
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Dick Ginga
>> Build Engineer
>> rgi...@disruptorbeam.com
>>
>> --
> 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/786bd114-b540-45c7-aebf-27e2c44a7029%40googlegroups.
> com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Dick Ginga
Build Engineer
rgi...@disruptorbeam.com

-- 
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/CAL3PpaWfxxjtt2D_nrc%3DaLyHBq_vzTTnNZXJ1mZNc_Y_ToUwug%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Multijob out of memory issues

2017-08-24 Thread Michael Pailloncy

The best to start here would be to try instructions on this page

and analyze the resulting heapdump.



2017-08-24 8:08 GMT+02:00 Shashank Bhargav :

> Hi All,
>
> We are facing serious out of memory errors with Multi job project.
>
> Configuration contains the following :
>
> 1. Parameterized build
> 2. Multi job Phase
> 3. Inject passwords to the build as environment variables
> 4. Set Jenkins user build variables
> 5. Editable Email notification
>
> All of these is executed ,memory immediately shoots up after last step  is
> executed and Jenkins hangs.
>
> Has anyone faced such issues before?
>
> --
> 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/2f7997c8-094c-4ab1-9888-47d354ad3c80%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/CAPO77c0PHO4X0XqW%3DSJ_gbXT1XH0zc75cRTynMFndyAOs5_4rg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Ansible role for installing and configuring Jenkins 2

2017-08-24 Thread A Drake

Karl, this was extremely helpful. THanks very much.

-- 
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/3bffd5b4-8c96-4339-833f-91205cc31171%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

readJSON file in new titandb with same vertexIds in writeJSON file

2017-08-24 Thread padmasrinijana via Jenkins Users

graph=TitanFactory.open('titan.properties')
graph.io(IoCore.graphson()).writeGraph("titan-graph.json");
 one sample row from titan-graph.json:(with vertexID: 49280)

{"id":49280,"label":"name","outE":{"edgeName":[{"id":"18nk-120w-5wk5-kbmld4","inV":1228853416,"properties":{"col1":49280}}]},"properties":{"col2":[{"id":"16a8-120w-31tx","value":"value2"}],"col3":[{"id":"15w0-120w-5on9","value":"val3"}],"col4":[{"id":"16og-120w-5nut","value":"val4"}],"col5":[{"id":"172o-120w-40lh","value":"val5"}]}}

example:
labelA:(vertexA)-with vertexid 42890
LabelB:(vertexB)-with vertexid 43456
LabelAB:(42890,43456)---storing vertexId of vertexA and vertexB

graph=TitanFactory.open('titan-new.properties')
graph.io(IoCore.graphson()).readGraph("titan-graph.json");

after reading from new titan graph db, the vertexids are different from the 
old one like below:
example:
labelA:(vertexA)-with vertexid 23434
LabelB:(vertexB)-with vertexid 34234
LabelAB:(42890,43456)---This is same copy as old one

As we are storing vertexIds of one label in another label,
am I missing something while reading or Is there any way to create vertex 
with same vertexId when reading the JSON in new titandb(becoz JSON has 
vertexIds and edgeIds)?

-- 
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/fb33fe2f-b62e-40f7-b215-d46b61a341fd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins crashes with "Illegal character 0x0 for HttpChannelOverHttp" - Why?

2017-08-24 Thread R. Tyler Croy

(replies inline)

On Fri, 10 Feb 2017, daniel.seeba...@gmail.com wrote:

> Hi,
> 
> - Ubuntu 16.04.1
> - Jenkins 2.32.2
> 
> Since a few days I see crashes on Jenkins: (/var/log/jenkins/jenkins.log*)*
> 
> Feb 10, 2017 12:15:09 AM hudson.security.csrf.CrumbFilter doFilter
> WARNING: No valid crumb was included in request for /azenv.php. Returning 
> 403.


For what it's worth, I have been seeing this a bit lately as well. As far as I
can tell (https://bugs.eclipse.org/bugs/show_bug.cgi?id=471081) it's due to
something attempting to speak HTTPs to an HTTP only service.




> 
> Feb 10, 2017 2:06:33 AM org.eclipse.jetty.util.log.JavaUtilLog warn
> WARNING: Illegal character 0x1 in state=START for buffer 
> HeapByteBuffer@6de2eef2[p=1,l=256,c=16384,r=255]={\x01<<<\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01...\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01>>>.com/\r\nContent-Ty...\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00}
> Feb 10, 2017 2:06:33 AM org.eclipse.jetty.util.log.JavaUtilLog warn
> WARNING: badMessage: 400 Illegal character 0x1 for 
> HttpChannelOverHttp@10d1bddb{r=0,c=false,a=IDLE,uri=}
> 
> Feb 10, 2017 4:35:15 AM hudson.security.csrf.CrumbFilter doFilter
> WARNING: No valid crumb was included in request for /azenv.php. Returning 
> 403.
> 
> Feb 10, 2017 5:30:24 AM org.eclipse.jetty.util.log.JavaUtilLog warn
> WARNING: Illegal character 0x0 in state=START for buffer 
> HeapByteBuffer@5e57ec7c[p=1,l=1,c=16384,r=0]={\x00<<<>>>ET /login 
> HTTP/1\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00}
> Feb 10, 2017 5:30:24 AM org.eclipse.jetty.util.log.JavaUtilLog warn
> WARNING: badMessage: 400 Illegal character 0x0 for 
> HttpChannelOverHttp@1910d1bc{r=0,c=false,a=IDLE,uri=}
> Feb 10, 2017 5:30:25 AM org.eclipse.jetty.util.log.JavaUtilLog warn
> WARNING: Illegal character 0x4 in state=START for buffer 
> HeapByteBuffer@53c389d4[p=1,l=10,c=16384,r=9]={\x04<<<\x01\x00P\xC0c\xF660\x00>>>/m.sogou.com/?ran...\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00}
> Feb 10, 2017 5:30:25 AM org.eclipse.jetty.util.log.JavaUtilLog warn
> WARNING: badMessage: 400 Illegal character 0x4 for 
> HttpChannelOverHttp@3e824b3e{r=0,c=false,a=IDLE,uri=}
> Feb 10, 2017 5:30:25 AM org.eclipse.jetty.util.log.JavaUtilLog warn
> WARNING: Illegal character 0x4 in state=START for buffer 
> HeapByteBuffer@64380bcf[p=1,l=10,c=16384,r=9]={\x04<<<\x01\x00P\xC0c\xF660\x00>>>
>  
> HTTP/1.1\r\nUser-A...\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00}
> Feb 10, 2017 5:30:25 AM org.eclipse.jetty.util.log.JavaUtilLog warn
> WARNING: badMessage: 400 Illegal character 0x4 for 
> HttpChannelOverHttp@605ff7ac{r=0,c=false,a=IDLE,uri=}
> Feb 10, 2017 5:30:25 AM org.eclipse.jetty.util.log.JavaUtilLog warn
> WARNING: Illegal character 0x5 in state=START for buffer 
> HeapByteBuffer@53c389d4[p=1,l=3,c=16384,r=2]={\x05<<<\x01\x00>>>P\xC0c\xF660\x00/m.sogou.c...\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00}
> Feb 10, 2017 5:30:25 AM org.eclipse.jetty.util.log.JavaUtilLog warn
> WARNING: badMessage: 400 Illegal character 0x5 for 
> HttpChannelOverHttp@59989f5a{r=0,c=false,a=IDLE,uri=}
> 
> 
> Anyone can help or have ideas how to solve this? 
> 
> -- 
> 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/9aacc222-8133-4ca6-bb75-254ba142%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.


- R. Tyler Croy

--
 Code: 
  Chatter: 
 xmpp: rty...@jabber.org

  % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
--

-- 
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/20170824061209.u3c5dolrgcytuoff%40blackberry.coupleofllamas.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: PGP signature

Multijob out of memory issues

2017-08-24 Thread Shashank Bhargav

Hi All,

We are facing serious out of memory errors with Multi job project.

Configuration contains the following : 

1. Parameterized build
2. Multi job Phase
3. Inject passwords to the build as environment variables
4. Set Jenkins user build variables
5. Editable Email notification

All of these is executed ,memory immediately shoots up after last step  is 
executed and Jenkins hangs.

Has anyone faced such issues before?

-- 
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/2f7997c8-094c-4ab1-9888-47d354ad3c80%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.