Skip to content
This repository has been archived by the owner on Jul 23, 2020. It is now read-only.

Wildfly Red Hat Boosters Fail on Jenkins PR Build #4146

Closed
tinakurian opened this issue Aug 8, 2018 · 6 comments
Closed

Wildfly Red Hat Boosters Fail on Jenkins PR Build #4146

tinakurian opened this issue Aug 8, 2018 · 6 comments

Comments

@tinakurian
Copy link

When enabling Red Hat Wildfly boosters Jenkins builds fail for pull requests.

See attached logs.

wildflyredhat-http.txt
wildflyredhat-config.txt
wildflyredhat-health.txt

@ldimaggi
Copy link
Collaborator

ldimaggi commented Aug 8, 2018

Behavior that I am seeing is:

  • Create new app - select REST/Thorntail
  • Observe successful completion of build pipeline
  • Clone git repo for new app
  • Create pull request
  • Observe build pipeline initiated when the pull request is merged

@tinakurian
Copy link
Author

@ldimaggi Hey Len, this is for boosters with Red Hat Wildfly enabled, not for REST/Thorntail.

@bartoszmajsak
Copy link
Contributor

@ldimaggi PR builds will fail regardless, because they are executed in the wrong namespace fabric8io/fabric8-pipeline-library#412

Tina's work is based on the patched pipeline running tests in user namespace instead and usng Red Hat boosters, not community ones we expose on OSIO right now.

@stevengutz stevengutz added priority/P2 High and removed priority/P3 Medium labels Aug 14, 2018
@stevengutz
Copy link
Collaborator

@sthaha @pradeepto This is blocking Tina's progress on booster so I'm bumping the priority to P2. This needs to get fixed ASAP (next sprint or sooner)

@bartoszmajsak
Copy link
Contributor

bartoszmajsak commented Aug 14, 2018

@stevengutz It is not a problem of build team per se. This is a particular version of a runtime which is having a problem with our limited infra. I think it's not worth an effort looking at those as we can live with Thorntail (community version of WF Swarm) which have those issues fixed.

@slemeur can correct me if I'm wrong here wrt community vs product in this case.

@bartoszmajsak
Copy link
Contributor

We are going to stick with the community versions hence closing this issue as it's related to a particular version of the runtime and OSIO infra.

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

No branches or pull requests

4 participants