Warnings Next Generation Plugin With GCC C++

How do I use this plugin to record and show C/C++ Warnings/Errors from GCC? There is two tools available GNU C Compiler (gcc3) and GNU C Compiler (gcc4), but are those for C? We are using a much newer version of GCC. Otherwise I could only find these for C++ recordIssues(tools: [cppCheck()]) rec

Re: Warnings Next Generation Plugin With GCC C++

> Am 06.05.2019 um 12:27 schrieb Sverre Moe : > > How do I use this plugin to record and show C/C++ Warnings/Errors from GCC? > > There is two tools available GNU C Compiler (gcc3) and GNU C Compiler (gcc4), > but are those for C? > We are using a much newer version of GCC. > I think I shoul

Re: Warnings Next Generation Plugin With GCC C++

It seems to be very confused. I am bulding on 4 nodes opensuse42.3 opensuse15.0 sles12.3 sles15.0 They have each their own gcc4 ID, but they have the same result, showing the same 4 entries for each. Total 5 /dev/shm/rpmroot-build-opensuse42.3_x86_64/projectA/BUILD/projectA-1.3.2/something/some_

Re: Warnings Next Generation Plugin With GCC C++

mandag 6. mai 2019 12.55.15 UTC+2 skrev Ullrich Hafner følgende: > > > > I think I should rename the Tools > > GNU C Compiler (gcc4) -> GNU C Compiler > GNU C Compiler (gcc3) -> GNU C Compiler (3 and older) > > And the ID to gcc. > > Would that make sense? > > That makes sense. -- You received

Re: Warnings Next Generation Plugin With GCC C++

I think the tool Reads the complete output (where all 4 nodes are intermingled). It would be better if it could read only for the one node it is executed within. Still I find it odd that it showed the same issues for all nodes. It should at least show the ones from the node itself sles12.3 outpu

Re: Warnings Next Generation Plugin With GCC C++

There are some open issues about that: https://issues.jenkins-ci.org/browse/JENKINS-44450 https://issues.jenkins-ci.org/browse/JENKINS-55258 As a workaround you should pipe the log to a file

Some custom pipeline steps I created

I'v been using some custom steps a lot lately and I though it was time to share them :) https://github.com/roel0/jenkins-util-scripts Some of the API's provided: - Add/Remove environment variabels to a node - Delete jobs based on a condition - Fetch plotting data form the current

bitbucket-branch-source-plugin number of parallel scans limited to five

Hello I'm using jenkins 2.150.2 and bitbucket branch source plugin 2.4.0 when scan of repositories is performed : *Building » Scan Organization Folder*it is impossible to have more than 5 operations in parallel on the master, do you know if this limit is set somewhere or how it is computed ?

Re: bitbucket-branch-source-plugin number of parallel scans limited to five

I don't really understand your question. Can you be more specific? On Mon, May 6, 2019 at 8:22 PM Tristan FAURE wrote: > Hello > I'm using jenkins 2.150.2 and bitbucket branch source plugin 2.4.0 > > when scan of repositories is performed : > > > > *Building » Scan Organization Folder*it is > i

Re: bitbucket-branch-source-plugin number of parallel scans limited to five

Sorry if it is not clear when I create multi branch pipeline jobs for bitbuckets, scan of repositories (organization) is made frequently. For some repositories the number of projects, branches... can be important and the scan operation performed on the master can be long. When these scan opera

Re: Warnings Next Generation Plugin With GCC C++

mandag 6. mai 2019 13.23.02 UTC+2 skrev Ullrich Hafner følgende: > > There are some open issues about that: > https://issues.jenkins-ci.org/browse/JENKINS-44450 > https://issues.jenkins-ci.org/browse/JENKINS-55258 > > As a workaround you should pipe the log to a file. > How so, is there a pipelin

Re: Warnings Next Generation Plugin With GCC C++

> Am 06.05.2019 um 14:47 schrieb Sverre Moe : > > mandag 6. mai 2019 13.23.02 UTC+2 skrev Ullrich Hafner følgende: > There are some open issues about that: > https://issues.jenkins-ci.org/browse/JENKINS-44450 > > https://issues.jenkins-ci.org

Re: Error : Unable to load maven-metadata.xml while executing Jenkins project

the error you are getting is artifactory is saying the user running the build needs to give it some credentials (401) not sure how you configure Gradle to use username/password for repositories, but if you start there you should find your answer. /Janes On Fri, 3 May 2019, 12:13 , wrote: > Whi

Re: Jenkins JUnit Plugin - Unstable issues

I am sorry but I think your message seems blank. Did you write something? On Tuesday, April 30, 2019 at 6:21:11 AM UTC-7, Ullrich Hafner wrote: > > > > Am 29.04.2019 um 22:25 schrieb cliffha...@gmail.com : > > JUnit is defintiely setting the build status to UNSTABLE when the only > test which got

Jenkins Scripted Multi-branch Pipeline: Is it possible to have different build numbering schemes?

Hi, Am looking at having different build numbering schemes - one for timer triggered and another for builds triggered via git events. As of now, I cannot install any new plugin as that might force us to upgrade Jenkins -- ours is quite older version and the upgrade is long overdue. However, am