OpenBokeron/TallerCiCd
10
0
Fork 0
Code Issues Pull Requests Actions Packages Projects 1 Releases Wiki Activity

Jenkins Multibranch no ejecuta builds en pushes a Pull Requests (webhook PR sync ignorado) #34

New Issue
Closed
opened 2026-02-15 19:44:44 +01:00 by husbando_enjoyer · 2 comments
husbando_enjoyer commented 2026-02-15 19:44:44 +01:00
Owner
Copy Link

Cuando se abre una Pull Request, Jenkins lanza correctamente el build inicial.
Pero si posteriormente se realiza un nuevo push sobre la rama de esa PR (evento sync), Jenkins:

  • recibe el webhook (HTTP 200)
  • pero no dispara ningún build
  • y no aparece ningún evento en el log del plugin
    Provoca que los commits nuevos en una PR no se validen automáticamente.
Cuando se abre una Pull Request, Jenkins lanza correctamente el build inicial. Pero si posteriormente se realiza un nuevo `push` sobre la rama de esa PR (evento `sync`), Jenkins: - recibe el webhook (HTTP 200) - pero no dispara ningún build - y no aparece ningún evento en el log del plugin Provoca que los commits nuevos en una PR no se validen automáticamente.
husbando_enjoyer added the Kind/Bug
Priority
Critical
1
 labels 2026-02-15 19:44:44 +01:00
husbando_enjoyer self-assigned this 2026-02-15 19:44:44 +01:00
husbando_enjoyer added this to the TallerCI/CD - Jenkins project 2026-02-15 19:44:44 +01:00
husbando_enjoyer commented 2026-02-15 19:49:16 +01:00
Author
Owner
Copy Link

Ocurría porque Gitea tenía configurado como ROOT_URL=openbokeron.org, en vez de openbokeron.uma.es. A pesar de que en la mayor parte de las ocasiones funcionaba el webhook, ha dado la casualidad de que esa incongruencia provocaba error. Se corrige parámetro de Gitea solucionando la problemática.

Se hace necesario actualizar Jenkinsfile.ci para lanzar comentarios usando openbokeron.uma.es con la API de Gitea.

Ocurría porque Gitea tenía configurado como `ROOT_URL=openbokeron.org`, en vez de `openbokeron.uma.es`. A pesar de que en la mayor parte de las ocasiones funcionaba el webhook, ha dado la casualidad de que esa incongruencia provocaba error. Se corrige parámetro de Gitea solucionando la problemática. Se hace necesario actualizar `Jenkinsfile.ci` para lanzar comentarios usando `openbokeron.uma.es` con la API de Gitea.
husbando_enjoyer moved this to In Progress in TallerCI/CD - Jenkins on 2026-02-15 20:04:08 +01:00
husbando_enjoyer commented 2026-02-16 21:04:27 +01:00
Author
Owner
Copy Link

Solucionado.

Solucionado.
husbando_enjoyer moved this to Done in TallerCI/CD - Jenkins on 2026-02-16 21:04:38 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Compat/Breaking
Breaking change that won't be backward compatible
 Kind/Bug
Something is not working
 Kind/Documentation
Documentation changes
 Kind/Enhancement
Improve existing functionality
 Kind/Feature
New functionality
 Kind/Security
This is security issue
 Kind/Testing
Issue or pull request related to testing
Priority
Critical
1
The priority is critical
Priority
High
2
The priority is high
Priority
Low
4
The priority is low
Priority
Medium
3
The priority is medium
Reviewed
Confirmed
1
Issue has been confirmed
Reviewed
Duplicate
2
This issue or pull request already exists
Reviewed
Invalid
3
Invalid issue
Reviewed
Won't Fix
3
This issue won't be fixed
Status
Abandoned
3
Somebody has started to work on this but abandoned work
Status
Blocked
1
Something is blocking this issue or pull request
Status
Need More Info
2
Feedback is required to reproduce issue or to continue work
No Label Kind/Bug
Priority
Critical
1
Milestone
No items
No Milestone
Projects
Clear projects
No project TallerCI/CD - Jenkins
Assignees
Clear assignees
Abdulee Chacluclu ferreiro husbando_enjoyer jenkins-bot Josetronco makrron MiguelMJ nameless nestorlora workshop_user
No Assignees husbando_enjoyer
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: OpenBokeron/TallerCiCd#34
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?