SVN Poll SCM not working

Using Jenkins
1
Jenkins setup (click to expand): 
Jenkins: 2.424
OS: Linux - 4.18.0-477.27.1.el8_8.x86_64
Java: 11.0.19 - Azul Systems, Inc. (OpenJDK 64-Bit Server VM)
---
42crunch-security-audit:5.3
ant:481.v7b_09e538fcca
ant-in-workspace:1.2.2
antisamy-markup-formatter:162.v0e6ec0fcfcf6
apache-httpcomponents-client-4-api:4.5.14-208.v438351942757
bootstrap5-api:5.3.0-1
bouncycastle-api:2.28
branch-api:2.1071.v1a_188a_562481
build-timeout:1.31
caffeine-api:3.1.8-133.v17b_1ff2e0599
checks-api:2.0.0
cloudbees-folder:6.848.ve3b_fd7839a_81
command-launcher:100.v2f6722292ee8
commons-lang3-api:3.13.0-62.v7d18e55f51e2
commons-text-api:1.10.0-68.v0d0b_c439292b_
config-file-provider:959.vcff671a_4518b_
credentials:1271.v54b_1c2c6388a_
credentials-binding:636.v55f1275c7b_27
display-url-api:2.3.9
durable-task:523.va_a_22cf15d5e0
echarts-api:5.4.0-5
email-ext:2.100
email-ext-recipients-column:27.vb_9404db_b_018d
emailext-template:1.5
font-awesome-api:6.4.0-2
git:5.2.0
git-client:4.5.0
github:1.37.3
github-api:1.314-431.v78d72a_3fe4c3
github-branch-source:1732.v3f1889a_c475b_
gradle:2.8.2
h2-api:1.4.199
instance-identity:173.va_37c494ec4e5
ionicons-api:56.v1b_1c8c49374e
jackson2-api:2.15.2-350.v0c2f3f8fc595
jakarta-activation-api:2.0.1-3
jakarta-mail-api:2.0.1-3
javadoc:243.vb_b_503b_b_45537
javax-activation-api:1.2.0-6
javax-mail-api:1.6.2-9
jaxb:2.3.8-1
jdk-tool:66.vd8fa_64ee91b_d
jjwt-api:0.11.5-77.v646c772fddb_0
jquery3-api:3.7.0-1
jsch:0.2.8-65.v052c39de79b_2
junit:1217.v4297208a_a_b_ce
ldap:694.vc02a_69c9787f
mailer:463.vedf8358e006b_
mapdb-api:1.0.9-28.vf251ce40855d
matrix-auth:3.1.10
matrix-project:808.v5a_b_5f56d6966
maven-plugin:3.23
mina-sshd-api-common:2.10.0-69.v28e3e36d18eb_
mina-sshd-api-core:2.10.0-69.v28e3e36d18eb_
okhttp-api:4.11.0-157.v6852a_a_fa_ec11
pam-auth:1.10
pipeline-build-step:505.v5f0844d8d126
pipeline-github-lib:42.v0739460cda_c4
pipeline-graph-analysis:202.va_d268e64deb_3
pipeline-groovy-lib:656.va_a_ceeb_6ffb_f7
pipeline-input-step:468.va_5db_051498a_4
pipeline-maven:1298.v43b_82f220a_e9
pipeline-milestone-step:111.v449306f708b_7
pipeline-model-api:2.2144.v077a_d1928a_40
pipeline-model-definition:2.2144.v077a_d1928a_40
pipeline-model-extensions:2.2144.v077a_d1928a_40
pipeline-project-env:102.vdb_44a_6154b_88
pipeline-rest-api:2.33
pipeline-stage-step:305.ve96d0205c1c6
pipeline-stage-tags-metadata:2.2144.v077a_d1928a_40
pipeline-stage-view:2.33
plain-credentials:143.v1b_df8b_d3b_e48
plugin-util-api:3.3.0
pollscm:1.5
publish-over:0.22
publish-over-ssh:1.25
resource-disposer:0.23
scm-api:676.v886669a_199a_a_
script-security:1275.v23895f409fb_d
snakeyaml-api:1.33-95.va_b_a_e3e47b_fa_4
ssh-credentials:308.ve4497b_ccd8f4
ssh-slaves:2.916.vd17b_43357ce4
sshd:3.303.vefc7119b_ec23
structs:325.vcb_307d2a_2782
subversion:2.17.3
testng-plugin:794.ve7e315837b_b_3
token-macro:384.vf35b_f26814ec
trilead-api:2.84.v72119de229b_7
variant:59.vf075fe829ccb
workflow-aggregator:596.v8c21c963d92d
workflow-api:1283.v99c10937efcb_
workflow-basic-steps:1017.vb_45b_302f0cea_
workflow-cps:3793.v65dec41c3a_c3
workflow-durable-task-step:1289.v4d3e7b_01546b_
workflow-job:1348.v32a_a_f150910e
workflow-multibranch:746.v05814d19c001
workflow-scm-step:415.v434365564324
workflow-step-api:639.v6eca_cd8c04a_a_
workflow-support:865.v43e78cc44e0d
ws-cleanup:0.45

Good afternoon mam/sir

Currently I am working on a project in which servers are strictly controlled. Since there was no internet connection provided to the server I installed Jenkins via jenkins.war file from Jenkins official site.

I’ll brief you about the environment I am currently working in.
I have configured Jenkins and jenkins’ node. Let’s say Jenkins controller is configured in server 1 and node in server 2. I am using subversion for SCM. I configure SVN on https via self signed certificate on server 2 (On jenkins node)

I manually uploaded the plugins, and everything seems to be working fine except the Jenkins trigger (PollSCM).

In the polling log it says no changes even after committing.

The pipeline starts and builds the file successfully when run manually through build now option. Even build periodically is working just fine. It is just Poll SCM which is not working.

Kindly help me out so that i can resolve this issue

2

Hello @Kevinjosetom and welcome to this community. :wave:

Nothing to do with your problem, but your kernel is really old… I understand when you write “strictly controlled”.
There are maybe a few things you could check and troubleshoot:

  1. Check Polling Schedule: Make sure that your job’s polling schedule is configured correctly. If you are using Poll SCM, you should specify how often Jenkins should check for changes in your Subversion repository. If you have set this schedule correctly and it’s still not working, try running the job more frequently for testing purposes. :thinking:
  2. Workspace Location: Verify that the workspace (working directory) where Jenkins checks out your code is clean and doesn’t have any unversioned or ignored files that might cause the polling to fail.
  3. Credentials: Ensure that the credentials used to access your Subversion repository are correctly configured. Jenkins needs the appropriate credentials to access the repository and perform the polling.
  4. Check Polling Log: Check the polling log (in the job’s build history) to see if there are any error messages or warnings that could provide information about why polling is not working as expected. Also, check the global Jenkins log.
  5. Plugin Version: Make sure that you are using a compatible version of the Subversion plugin with your Jenkins version. Out-of-date plugins can sometimes cause issues.
  6. Firewall and Network Issues: Since your Jenkins server is running in a controlled environment, ensure there are no firewall or network restrictions preventing Jenkins from reaching your Subversion repository. This could be the reason why manual builds and Build Periodically work, but Poll SCM does not.
  7. Subversion Configuration: Double-check your Subversion configuration within Jenkins. Ensure that the URL for the Subversion repository is correctly specified in your job configuration.
  8. Node Configuration: If your Jenkins job is configured to run on a specific node (server 2 in your case), verify that this node is correctly set up and able to reach the Subversion repository.
  9. Workspace Cleanup: Consider adding a workspace cleanup step to your Jenkins job configuration. This can help ensure that the workspace is clean before polling for changes.
  10. Console Output: Check the console output of your Jenkins job after a Poll SCM run. It might provide additional information or errors related to the polling operation.
  11. Plugin Logs: If that is even possible, enable detailed logs for the Subversion plugin. This could provide more insights into the polling process.
  12. Job Configuration: If you have complex job configurations, review them carefully. Make sure there are no conflicting settings or custom scripts that might interfere with the polling process.
3

Thank you @poddingue for taking out time and replying. I am kinda new to this so if can explain me how pollSCM checks for new commit in svn and all so that i can figure out at what level it is being blocked it would be of great help.
I am assuming that since all ports and URLs are blocked it must be causing this issue. But if i know how exactly Jenkins’ pollSCM work I will be able to resolve this issue.(Like does uses some network protocol to check new commit etc)
Thank you so much much for being so patient with me.
P.S I hope you are able to understand what i am trying to ask you. I am so sorry for not being precise with technical terms and convey the issue in a better fashion.