Re: Building Jenkins-plugins failed in maven enforcer plugins

[Ullrich Hafner]

Which maven version are you using? The error message says that you need to use 
at least Maven 3.8.1.

> Am 30.01.2023 um 07:37 schrieb Ahmed Rafiq :
> 
> Hello,
> trying to update our inhouse Jenkins plugins. But it gets failed from 
> maven-enforcer-plugin at
> 
> [ERROR] Rule 1: org.apache.maven.plugins.enforcer.RequireMavenVersion failed 
> with message:
> 3.8.1 required to no longer download dependencies via HTTP (use HTTPS 
> instead).
> 
> In our settings.xml and POM.xml there's no dependencies with HTTP url, 
> therefore quite confused where to solve / debug for this error.
> 
> Can anyone give me some ideas?
> 
> Thanks.
> 
> -- 
> 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/CAOxCx6%3DPjBJaREhmwdW5NVGKW%2BahvxApkCw1c6AovyH0pSdTUw%40mail.gmail.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/FD82F910-F032-4BA5-BABF-6F2033DAE061%40gmail.com.

Building Jenkins-plugins failed in maven enforcer plugins

[Ahmed Rafiq]

Hello,
trying to update our inhouse Jenkins plugins. But it gets failed from
maven-enforcer-plugin at


*[ERROR] Rule 1: org.apache.maven.plugins.enforcer.RequireMavenVersion
failed with message:3.8.1 required to no longer download dependencies via
HTTP (use HTTPS instead).*

In our *settings.xml* and *POM.xml* there's no dependencies with HTTP url,
therefore quite confused where to solve / debug for this error.

Can anyone give me some ideas?

Thanks.

-- 
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/CAOxCx6%3DPjBJaREhmwdW5NVGKW%2BahvxApkCw1c6AovyH0pSdTUw%40mail.gmail.com.

Re: Contexts/environments?

[Mark Waite]

On Sunday, January 29, 2023 at 8:38:58 PM UTC-7 Victor Sudakov wrote:
Any ideas or thoughts on this? 

On 27.01.2023 16:42, Victor Sudakov wrote: 
> Dear Colleagues, 
> 
> Some CI/CD tools support the concept of contexts or environments. In each 
> environment/context, you define a set of variables or secrets with 
> different values, and refer to the contexts from the pipeline. For 
example, 
> for Github Actions you can create the "main" and "dev" environments and 
> then mention them in your pipeline: 


I've used folders as a way to provide additional context for a job.  If one 
folder is for dev and another is for main, the environment variables on the 
main folder can be different than the environment variables on the dev 
folder.  Credentials can be assigned to the folder as well.  If the same 
credential ID is used in both contexts, the job should be able to reference 
credentials from the folder.

 
> jobs: 
> build: 
> runs-on: ubuntu-latest 
> environment: ${{ github.ref_name }} 
> steps: 
> - name: Test secrets 
> run: something 
> env: 
> SUPER_SECRET: ${{ secrets.TEST_SECRET }} 
> 
> and the value of secrets.TEST_SECRET will be different for different 
> branches. 
> 
> Do you know of a plugin for Jenkins with a similar functionality for its 
> Multibranch Pipelines? 
> 
> Jenkins has the concept of "credential domains", can they be used for 
this 
> purpose (like referring to a credential domain from the environment{} 
block for 
> example)? 
> 
-- 
Victor Sudakov 
Systems Administrator 
Streamline - Property Management Software 
Website: www.streamlinevrs.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/bbc6dd83-232a-445c-bed9-672728b1047bn%40googlegroups.com.

Re: Contexts/environments?

[Victor Sudakov]

Any ideas or thoughts on this?

On 27.01.2023 16:42, Victor Sudakov wrote:

Dear Colleagues,

Some CI/CD tools support the concept of contexts or environments. In each
environment/context, you define a set of variables or secrets with
different values, and refer to the contexts from the pipeline. For example,
for Github Actions you can create the "main" and "dev" environments and
then mention them in your pipeline:

jobs:
   build:
 runs-on: ubuntu-latest
 environment: ${{ github.ref_name }}
 steps:
   - name: Test secrets
 run: something
 env:
   SUPER_SECRET: ${{ secrets.TEST_SECRET }}

and the value of secrets.TEST_SECRET will be different for different
branches.

Do you know of a plugin for Jenkins with a similar functionality for its
Multibranch Pipelines?

Jenkins has the concept of "credential domains", can they be used for this
purpose (like referring to a credential domain from the environment{} block for
example)?


--
Victor Sudakov
Systems Administrator
Streamline - Property Management Software
Website: www.streamlinevrs.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/e91642d7-3e80-4b81-ca2b-481f74aa9a21%404vrs.com.