logo
down
shadow

After changing Maricurial url in hgrc, jenkins stuck on pull


After changing Maricurial url in hgrc, jenkins stuck on pull

By : wabafit
Date : November 22 2020, 10:56 AM
fixed the issue. Will look into that further As I mentioned in my question that I recently changed repository url. The issue was that new server's key was not cached in the registry where jenkins was hosted.
Resolution:
code :


Share : facebook icon twitter icon
How can I get 'hg pull' to honor trusted-users section in my .hgrc?

How can I get 'hg pull' to honor trusted-users section in my .hgrc?


By : Michael Joe
Date : March 29 2020, 07:55 AM
around this issue It's on the remote machine that the trust isn't established, and your local .hgrc only affects users on the local machine. Put the trust section line in your remote .hgrc (in your homedir on the machine where the remote repository lives). That, of course, assumes you're using 'ssh://' remote URLs. If you're using 'http://' URLs to access the repository then it's the .hgrc of the apache (or wwwuser or whatever) user on the remote machine that needs to assert trust.
Jenkins Pull Request Builder start build old closed pull requests

Jenkins Pull Request Builder start build old closed pull requests


By : Yur_Gens
Date : March 29 2020, 07:55 AM
fixed the issue. Will look into that further The JENKINS Multi-Branch Project Plugin, now JENKINS Pipeline Multibranch Plugin should be the one allowing to build only branches with new commits.
If you don't use that plugin, the refspec refs/remotes/origin/pr/* would select all PR branches.
Change multiple hgrc files from default = http to default = ssh and default-pull = http

Change multiple hgrc files from default = http to default = ssh and default-pull = http


By : Simon Gingins
Date : March 29 2020, 07:55 AM
I wish this helpful for you (N.B.: This is not really a Mercurial issue, it's mainly just a shell and sed issue, with a side effect of regular expression stuff. If you wanted to get particularly fancy, though, you might want to make sure that only default = http://... lines that are in a paths section are modified, and that requires much fancier work in sed, or using a real config-file reader.)
You have multiple issues here:
code :
echo (foo)
sh-3.2$ echo '(foo)'
(foo)
sh-3.2$ echo \(foo\)
(foo)
sh-3.2$ echo test | sed -e s/\\\(e.\*\\\)/captured\ \\\1/
tcaptured est
sh-3.2$ echo test | sed -e 's/\(e.*\)/captured \1/'
tcaptured est
default = http://whatever
sh-3.2$ echo test | sed -e 's/\(e.*\)/
> captured \1/'
sed: 1: "s/\(e.*\)/
captured \1/
": unescaped newline inside substitute pattern
sh-3.2$ echo test | sed -e 's/\(e.*\)/\
captured \1/'
t
captured est
sh-3.2$ echo default = http://foo > foo.txt
sh-3.2$ sed -e 's,^default = http://\(.*\),default = ssh://myusername@\1\
> default-push = http://\1,' < foo.txt
default = ssh://myusername@foo
default-push = http://foo
sh-3.2$ sed -i '' -e 's,^default = http://\(.*\),default = ssh://myusername@\1\
default-push = http://\1,' foo.txt
sh-3.2$ cat foo.txt
default = ssh://myusername@foo
default-push = http://foo
How can I build Docker images on Jenkins Pipeline, without changing permissions on the underlying Jenkins VM?

How can I build Docker images on Jenkins Pipeline, without changing permissions on the underlying Jenkins VM?


By : Krishna Krupa
Date : March 29 2020, 07:55 AM
hop of those help? The pipeline definition shown is trying to execute the docker build inside a docker container (google/cloud-sdk:latest). Instead you should do the following given the jenkins user on the host has permission to execute docker commands on the host.
code :
pipeline {
  agent  any
  stages {
    stage('deploy') {
      steps {    
        script {    
          docker.build  "gcr.io/myporject/mydockerimage:1"
        } 
      }
    }
  }
}
Jenkins integrating with Github Organization: on opened pull requests, only run build for pull request NOT for branches

Jenkins integrating with Github Organization: on opened pull requests, only run build for pull request NOT for branches


By : Edwin
Date : March 29 2020, 07:55 AM
I hope this helps you . If you add Filter by name (with regular expression) to Behaviours as develop|PR-.* it will stop triggering the pipeline for branches that doesn't match the pattern. screenshot
shadow
Privacy Policy - Terms - Contact Us © ourworld-yourmove.org