date:20190817

Re: Build failed in Jenkins: clerezza #1110

2019-08-17 Thread Hasan

Dear Ewen

The jenkins notification is supposed to be sent only to
comm...@clerezza.apache.org.


[image: image.png]

Best regards
Hasan

On Sat, Aug 17, 2019 at 4:41 AM Ewen Cheslack-Postava  wrote:

> You have your Jenkins job configured in a way that is spamming people
> unrelated to your project. I don't even know what Clarezza is or how my
> email address is getting included, but am being bombarded with build
> failure spam and will have to address with ASF infra team if this cannot be
> corrected. In general, you need to ensure these notifications use a
> whitelist to make them non-spammy for open source projects.
>
> Thanks,
> Ewen
>
> On Fri, Aug 16, 2019, at 4:29 PM, Apache Jenkins Server wrote:
> > See <
> https://builds.apache.org/job/clerezza/1110/display/redirect?page=changes>
> >
> > Changes:
> >
> > [Hasan] Add header information about usage in the file KEYS
> >
> > --
> > Started by an SCM change
> > No JDK named ?jdk-1.8.0? found
> > No JDK named ?jdk-1.8.0? found
> > [EnvInject] - Loading node environment variables.
> > No JDK named ?jdk-1.8.0? found
> > Building remotely on H27 (ubuntu xenial) in workspace
> > 
> > No JDK named ?jdk-1.8.0? found
> > No credentials specified
> > No JDK named ?jdk-1.8.0? found
> > Cloning the remote Git repository
> > Cloning repository https://git-wip-us.apache.org/repos/asf/clerezza.git
> >  > git init  # timeout=10
> > Fetching upstream changes from
> > https://git-wip-us.apache.org/repos/asf/clerezza.git
> >  > git --version # timeout=10
> >  > git fetch --tags --progress
> > https://git-wip-us.apache.org/repos/asf/clerezza.git
> > +refs/heads/*:refs/remotes/origin/*
> >  > git config remote.origin.url
> > https://git-wip-us.apache.org/repos/asf/clerezza.git # timeout=10
> >  > git config --add remote.origin.fetch
> > +refs/heads/*:refs/remotes/origin/* # timeout=10
> >  > git config remote.origin.url
> > https://git-wip-us.apache.org/repos/asf/clerezza.git # timeout=10
> > Fetching upstream changes from
> > https://git-wip-us.apache.org/repos/asf/clerezza.git
> >  > git fetch --tags --progress
> > https://git-wip-us.apache.org/repos/asf/clerezza.git
> > +refs/heads/*:refs/remotes/origin/*
> >  > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
> >  > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
> > No JDK named ?jdk-1.8.0? found
> > Checking out Revision 36ee89b73737fcc894aedfb29a44959cbe2edec4
> > (refs/remotes/origin/master)
> >  > git config core.sparsecheckout # timeout=10
> >  > git checkout -f 36ee89b73737fcc894aedfb29a44959cbe2edec4
> > Commit message: "Add header information about usage in the file KEYS"
> >  > git rev-list --no-walk 8576350a9b68128e4ebd929e557b4c8d1169a5e2 #
> > timeout=10
> > No JDK named ?jdk-1.8.0? found
> > [locks-and-latches] Checking to see if we really have the locks
> > [locks-and-latches] Have all the locks, build can start
> > No JDK named ?jdk-1.8.0? found
> > Parsing POMs
> > Modules changed, recalculating dependency graph
> > Established TCP socket on 46630
> > maven3-agent.jar already up to date
> > maven3-interceptor.jar already up to date
> > maven3-interceptor-commons.jar already up to date
> > [clerezza] $ java -XX:MaxPermSize=400m -Xss512k -Xmx1g -cp
> >
> /home/jenkins/jenkins-slave/maven3-agent.jar:/home/jenkins/tools/maven/apache-maven-3.0.5/boot/plexus-classworlds-2.4.jar
> org.jvnet.hudson.maven3.agent.Maven3Main
> /home/jenkins/tools/maven/apache-maven-3.0.5
> /home/jenkins/jenkins-slave/remoting.jar
> /home/jenkins/jenkins-slave/maven3-interceptor.jar
> /home/jenkins/jenkins-slave/maven3-interceptor-commons.jar 46630
> > Unrecognized VM option 'MaxPermSize=400m'
> > Error: Could not create the Java Virtual Machine.
> > Error: A fatal exception has occurred. Program will exit.
> > [locks-and-latches] Releasing all the locks
> > [locks-and-latches] All the locks released
> > ERROR: Failed to launch Maven. Exit code = 1
> > No JDK named ?jdk-1.8.0? found
> > No JDK named ?jdk-1.8.0? found
> > No JDK named ?jdk-1.8.0? found
> >
>

[jira] [Created] (CLEREZZA-1046) Update jenkins job

2019-08-17 Thread Hasan (JIRA)

Hasan created CLEREZZA-1046:
---

 Summary: Update jenkins job
 Key: CLEREZZA-1046
 URL: https://issues.apache.org/jira/browse/CLEREZZA-1046
 Project: Clerezza
  Issue Type: Improvement
Reporter: Hasan
Assignee: Hasan


No need to send separate notifications to each individual who broke the build.

Use gitbox.apache.org instead of git-wip-us.apache.org



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[jira] [Updated] (CLEREZZA-1046) Update jenkins job

2019-08-17 Thread Hasan (JIRA)



 [ 
https://issues.apache.org/jira/browse/CLEREZZA-1046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hasan updated CLEREZZA-1046:

Description: 
No need to send separate notifications to each individual who broke the build.

Use gitbox.apache.org instead of git-wip-us.apache.org

Use maven version 3.3.9

 

  was:
No need to send separate notifications to each individual who broke the build.

Use gitbox.apache.org instead of git-wip-us.apache.org


> Update jenkins job
> --
>
> Key: CLEREZZA-1046
> URL: https://issues.apache.org/jira/browse/CLEREZZA-1046
> Project: Clerezza
>  Issue Type: Improvement
>Reporter: Hasan
>Assignee: Hasan
>Priority: Major
>
> No need to send separate notifications to each individual who broke the build.
> Use gitbox.apache.org instead of git-wip-us.apache.org
> Use maven version 3.3.9
>  



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Re: Build failed in Jenkins: clerezza #1110

2019-08-17 Thread Hasan Hasan

Dear Ewen

Since you are not the one who broke the build, that settings should not
affect you.
But I remove that check now to be on the safe side.
I could not find any other configurations which might be the problem.

Regards
Hasan

On Sat, Aug 17, 2019 at 10:25 PM Ewen Cheslack-Postava 
wrote:

> That screenshot clearly shows at least one problem: "Send separate emails
> to individuals who broke the build" is checked in addition to the commits@
> target. But something else must be misconfigured because I am recieving the
> emails in addition to others and I have never had any association with your
> project.
>
> -Ewen
>
> On Fri, Aug 16, 2019, at 11:53 PM, Hasan wrote:
>
> Dear Ewen
>
> The jenkins notification is supposed to be sent only to
> comm...@clerezza.apache.org.
>
>
> [image: image.png]
>
> Best regards
> Hasan
>
> On Sat, Aug 17, 2019 at 4:41 AM Ewen Cheslack-Postava 
> wrote:
>
> You have your Jenkins job configured in a way that is spamming people
> unrelated to your project. I don't even know what Clarezza is or how my
> email address is getting included, but am being bombarded with build
> failure spam and will have to address with ASF infra team if this cannot be
> corrected. In general, you need to ensure these notifications use a
> whitelist to make them non-spammy for open source projects.
>
> Thanks,
> Ewen
>
> On Fri, Aug 16, 2019, at 4:29 PM, Apache Jenkins Server wrote:
> > See <
> https://builds.apache.org/job/clerezza/1110/display/redirect?page=changes>
> >
> > Changes:
> >
> > [Hasan] Add header information about usage in the file KEYS
> >
> > --
> > Started by an SCM change
> > No JDK named ?jdk-1.8.0? found
> > No JDK named ?jdk-1.8.0? found
> > [EnvInject] - Loading node environment variables.
> > No JDK named ?jdk-1.8.0? found
> > Building remotely on H27 (ubuntu xenial) in workspace
> > 
> > No JDK named ?jdk-1.8.0? found
> > No credentials specified
> > No JDK named ?jdk-1.8.0? found
> > Cloning the remote Git repository
> > Cloning repository https://git-wip-us.apache.org/repos/asf/clerezza.git
> >  > git init  # timeout=10
> > Fetching upstream changes from
> > https://git-wip-us.apache.org/repos/asf/clerezza.git
> >  > git --version # timeout=10
> >  > git fetch --tags --progress
> > https://git-wip-us.apache.org/repos/asf/clerezza.git
> > +refs/heads/*:refs/remotes/origin/*
> >  > git config remote.origin.url
> > https://git-wip-us.apache.org/repos/asf/clerezza.git # timeout=10
> >  > git config --add remote.origin.fetch
> > +refs/heads/*:refs/remotes/origin/* # timeout=10
> >  > git config remote.origin.url
> > https://git-wip-us.apache.org/repos/asf/clerezza.git # timeout=10
> > Fetching upstream changes from
> > https://git-wip-us.apache.org/repos/asf/clerezza.git
> >  > git fetch --tags --progress
> > https://git-wip-us.apache.org/repos/asf/clerezza.git
> > +refs/heads/*:refs/remotes/origin/*
> >  > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
> >  > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
> > No JDK named ?jdk-1.8.0? found
> > Checking out Revision 36ee89b73737fcc894aedfb29a44959cbe2edec4
> > (refs/remotes/origin/master)
> >  > git config core.sparsecheckout # timeout=10
> >  > git checkout -f 36ee89b73737fcc894aedfb29a44959cbe2edec4
> > Commit message: "Add header information about usage in the file KEYS"
> >  > git rev-list --no-walk 8576350a9b68128e4ebd929e557b4c8d1169a5e2 #
> > timeout=10
> > No JDK named ?jdk-1.8.0? found
> > [locks-and-latches] Checking to see if we really have the locks
> > [locks-and-latches] Have all the locks, build can start
> > No JDK named ?jdk-1.8.0? found
> > Parsing POMs
> > Modules changed, recalculating dependency graph
> > Established TCP socket on 46630
> > maven3-agent.jar already up to date
> > maven3-interceptor.jar already up to date
> > maven3-interceptor-commons.jar already up to date
> > [clerezza] $ java -XX:MaxPermSize=400m -Xss512k -Xmx1g -cp
> >
> /home/jenkins/jenkins-slave/maven3-agent.jar:/home/jenkins/tools/maven/apache-maven-3.0.5/boot/plexus-classworlds-2.4.jar
> org.jvnet.hudson.maven3.agent.Maven3Main
> /home/jenkins/tools/maven/apache-maven-3.0.5
> /home/jenkins/jenkins-slave/remoting.jar
> /home/jenkins/jenkins-slave/maven3-interceptor.jar
> /home/jenkins/jenkins-slave/maven3-interceptor-commons.jar 46630
> > Unrecognized VM option 'MaxPermSize=400m'
> > Error: Could not create the Java Virtual Machine.
> > Error: A fatal exception has occurred. Program will exit.
> > [locks-and-latches] Releasing all the locks
> > [locks-and-latches] All the locks released
> > ERROR: Failed to launch Maven. Exit code = 1
> > No JDK named ?jdk-1.8.0? found
> > No JDK named ?jdk-1.8.0? found
> > No JDK named ?jdk-1.8.0? found
> >
>
>
> *Attachments:*
>
>- image.png
>
>
>

[jira] [Resolved] (CLEREZZA-1046) Update jenkins job

2019-08-17 Thread Hasan (JIRA)



 [ 
https://issues.apache.org/jira/browse/CLEREZZA-1046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hasan resolved CLEREZZA-1046.
-
Resolution: Fixed

> Update jenkins job
> --
>
> Key: CLEREZZA-1046
> URL: https://issues.apache.org/jira/browse/CLEREZZA-1046
> Project: Clerezza
>  Issue Type: Improvement
>Reporter: Hasan
>Assignee: Hasan
>Priority: Major
>
> No need to send separate notifications to each individual who broke the build.
> Use gitbox.apache.org instead of git-wip-us.apache.org
> Use maven version 3.3.9
>  



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[jira] [Commented] (CLEREZZA-1047) Update version of org.apache.apache artifact in parent/pom.xml

2019-08-17 Thread Hasan (JIRA)



[ 
https://issues.apache.org/jira/browse/CLEREZZA-1047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16909838#comment-16909838
 ] 

Hasan commented on CLEREZZA-1047:
-

I tried using version 18 and got
{code:java}
$ mvn install
[INFO] Scanning for projects...
[INFO]     
[INFO] 
[INFO] Building Clerezza - Parent 8
[INFO] 
[INFO]
[INFO] --- maven-remote-resources-plugin:1.5:process (process-resource-bundles) 
@ clerezza ---
[INFO]
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ clerezza ---
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 0.944 s
[INFO] Finished at: 2019-08-18T00:09:30+02:00
[INFO] Final Memory: 13M/300M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process (default) on 
project clerezza: The parameters 'resourceBundles' for goal 
org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process are missing 
or invalid -> [Help 1]
[ERROR]

{code}

> Update version of org.apache.apache artifact in parent/pom.xml
> --
>
> Key: CLEREZZA-1047
> URL: https://issues.apache.org/jira/browse/CLEREZZA-1047
> Project: Clerezza
>  Issue Type: Improvement
>Reporter: Hasan
>Priority: Major
>
> Current version is 17. It is time to update to higher version
> {code:java}
>     
>     org.apache
>     apache
>     17
>      
>     
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Update version of org.apache.apache in parent/pom.xml

2019-08-17 Thread Hasan

Dear Reto and Furkan

Could you please try to increase the version of org.apache.apache
referred to in parent/pom.xml and then do a mvn install?
I got error when using version 18.

See issue https://issues.apache.org/jira/browse/CLEREZZA-1047

Could you please help fixing this? Thanks.

Cheers
Hasan

Re: Build failed in Jenkins: clerezza #1110

2019-08-17 Thread Ewen Cheslack-Postava

That screenshot clearly shows at least one problem: "Send separate emails to 
individuals who broke the build" is checked in addition to the commits@ target. 
But something else must be misconfigured because I am recieving the emails in 
addition to others and I have never had any association with your project.

-Ewen

On Fri, Aug 16, 2019, at 11:53 PM, Hasan wrote:
> Dear Ewen
> 
> The jenkins notification is supposed to be sent only to 
> comm...@clerezza.apache.org.
> 
> 
> image.png
> 
> Best regards
> Hasan
> 
> On Sat, Aug 17, 2019 at 4:41 AM Ewen Cheslack-Postava  wrote:
>> You have your Jenkins job configured in a way that is spamming people 
>> unrelated to your project. I don't even know what Clarezza is or how my 
>> email address is getting included, but am being bombarded with build failure 
>> spam and will have to address with ASF infra team if this cannot be 
>> corrected. In general, you need to ensure these notifications use a 
>> whitelist to make them non-spammy for open source projects.
>> 
>>  Thanks,
>>  Ewen
>> 
>>  On Fri, Aug 16, 2019, at 4:29 PM, Apache Jenkins Server wrote:
>>  > See 
>> 
>>  > 
>>  > Changes:
>>  > 
>>  > [Hasan] Add header information about usage in the file KEYS
>>  > 
>>  > --
>>  > Started by an SCM change
>>  > No JDK named ?jdk-1.8.0? found
>>  > No JDK named ?jdk-1.8.0? found
>>  > [EnvInject] - Loading node environment variables.
>>  > No JDK named ?jdk-1.8.0? found
>>  > Building remotely on H27 (ubuntu xenial) in workspace 
>>  > 
>>  > No JDK named ?jdk-1.8.0? found
>>  > No credentials specified
>>  > No JDK named ?jdk-1.8.0? found
>>  > Cloning the remote Git repository
>>  > Cloning repository https://git-wip-us.apache.org/repos/asf/clerezza.git
>>  > > git init  # timeout=10
>>  > Fetching upstream changes from 
>>  > https://git-wip-us.apache.org/repos/asf/clerezza.git
>>  > > git --version # timeout=10
>>  > > git fetch --tags --progress 
>>  > https://git-wip-us.apache.org/repos/asf/clerezza.git 
>>  > +refs/heads/*:refs/remotes/origin/*
>>  > > git config remote.origin.url 
>>  > https://git-wip-us.apache.org/repos/asf/clerezza.git # timeout=10
>>  > > git config --add remote.origin.fetch 
>>  > +refs/heads/*:refs/remotes/origin/* # timeout=10
>>  > > git config remote.origin.url 
>>  > https://git-wip-us.apache.org/repos/asf/clerezza.git # timeout=10
>>  > Fetching upstream changes from 
>>  > https://git-wip-us.apache.org/repos/asf/clerezza.git
>>  > > git fetch --tags --progress 
>>  > https://git-wip-us.apache.org/repos/asf/clerezza.git 
>>  > +refs/heads/*:refs/remotes/origin/*
>>  > > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
>>  > > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
>>  > No JDK named ?jdk-1.8.0? found
>>  > Checking out Revision 36ee89b73737fcc894aedfb29a44959cbe2edec4 
>>  > (refs/remotes/origin/master)
>>  > > git config core.sparsecheckout # timeout=10
>>  > > git checkout -f 36ee89b73737fcc894aedfb29a44959cbe2edec4
>>  > Commit message: "Add header information about usage in the file KEYS"
>>  > > git rev-list --no-walk 8576350a9b68128e4ebd929e557b4c8d1169a5e2 # 
>>  > timeout=10
>>  > No JDK named ?jdk-1.8.0? found
>>  > [locks-and-latches] Checking to see if we really have the locks
>>  > [locks-and-latches] Have all the locks, build can start
>>  > No JDK named ?jdk-1.8.0? found
>>  > Parsing POMs
>>  > Modules changed, recalculating dependency graph
>>  > Established TCP socket on 46630
>>  > maven3-agent.jar already up to date
>>  > maven3-interceptor.jar already up to date
>>  > maven3-interceptor-commons.jar already up to date
>>  > [clerezza] $ java -XX:MaxPermSize=400m -Xss512k -Xmx1g -cp 
>>  > 
>> /home/jenkins/jenkins-slave/maven3-agent.jar:/home/jenkins/tools/maven/apache-maven-3.0.5/boot/plexus-classworlds-2.4.jar
>>  org.jvnet.hudson.maven3.agent.Maven3Main 
>> /home/jenkins/tools/maven/apache-maven-3.0.5 
>> /home/jenkins/jenkins-slave/remoting.jar 
>> /home/jenkins/jenkins-slave/maven3-interceptor.jar 
>> /home/jenkins/jenkins-slave/maven3-interceptor-commons.jar 46630
>>  > Unrecognized VM option 'MaxPermSize=400m'
>>  > Error: Could not create the Java Virtual Machine.
>>  > Error: A fatal exception has occurred. Program will exit.
>>  > [locks-and-latches] Releasing all the locks
>>  > [locks-and-latches] All the locks released
>>  > ERROR: Failed to launch Maven. Exit code = 1
>>  > No JDK named ?jdk-1.8.0? found
>>  > No JDK named ?jdk-1.8.0? found
>>  > No JDK named ?jdk-1.8.0? found
>>  >
> 
> *Attachments:*
>  * image.png

[jira] [Created] (CLEREZZA-1047) Update version of org.apache.apache artifact in parent/pom.xml

2019-08-17 Thread Hasan (JIRA)

Hasan created CLEREZZA-1047:
---

 Summary: Update version of org.apache.apache artifact in 
parent/pom.xml
 Key: CLEREZZA-1047
 URL: https://issues.apache.org/jira/browse/CLEREZZA-1047
 Project: Clerezza
  Issue Type: Improvement
Reporter: Hasan


Current version is 17. It is time to update to higher version
{code:java}
    
    org.apache
    apache
    17
     
    

{code}



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Re: Build failed in Jenkins: clerezza #1110

[jira] [Created] (CLEREZZA-1046) Update jenkins job

[jira] [Updated] (CLEREZZA-1046) Update jenkins job

Re: Build failed in Jenkins: clerezza #1110

[jira] [Resolved] (CLEREZZA-1046) Update jenkins job

[jira] [Commented] (CLEREZZA-1047) Update version of org.apache.apache artifact in parent/pom.xml

Update version of org.apache.apache in parent/pom.xml

Re: Build failed in Jenkins: clerezza #1110

[jira] [Created] (CLEREZZA-1047) Update version of org.apache.apache artifact in parent/pom.xml

9 matches

Site Navigation

Mail list logo

Footer information