Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A temporary maven settings.xml file to build ks-jenkins #16

Closed
LinuxSuRen opened this issue Jan 7, 2021 · 3 comments · Fixed by #42
Closed

A temporary maven settings.xml file to build ks-jenkins #16

LinuxSuRen opened this issue Jan 7, 2021 · 3 comments · Fixed by #42

Comments

@LinuxSuRen
Copy link
Member

LinuxSuRen commented Jan 7, 2021

ks-jenkins still depend on some plugins which are not released to Jenkins Community. So it still needs a private maven settings.xml file. In case of anyone wants to build it, please see it below:

Please not forget to modify the username/password.

<settings>
  <servers>
     <server>
      <id>github-a</id>
      <username>your-github-id</username>
      <password>your-github-token</password>
    </server>
  </servers>
  <activeProfiles>
    <activeProfile>github</activeProfile>
  </activeProfiles>
  <profiles>
    <profile>
      <id>github</id>
      <repositories>
        <repository>
          <id>central</id>
          <url>https://repo1.maven.org/maven2</url>
          <releases><enabled>true</enabled></releases>
          <snapshots><enabled>true</enabled></snapshots>
        </repository>
        <repository>
          <id>github-a</id>
          <name>GitHub OWNER Apache Maven Packages</name>
          <url>https://maven.pkg.github.com/LinuxSuRen/jenkins-build-monitor-plugin</url>
        </repository>
      </repositories>
    </profile>
  </profiles>
</settings>

See also

artifactId: build-monitor-plugin

@shaowenchen
Copy link

After cleaning ~/.m2/repository/, it works.

@JohnNiang
Copy link
Member

I suggest pinning the top of this issue.

@LinuxSuRen
Copy link
Member Author

LinuxSuRen commented Apr 28, 2021

I suggest pinning the top of this issue.

Good idea.

By the way, we need to find a way to figure out how to fix this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants