[
https://issues.jboss.org/browse/WFLY-5793?page=com.atlassian.jira.plugin....
]
Radoslav Husar edited comment on WFLY-5793 at 4/3/18 3:36 AM:
--------------------------------------------------------------
The update to this is that we now manage documentation within the wildfly repo in master
branch, so any updates to the docs here do not need to run the whole CI -- probably only
some sort of 'doc lint'. So the time saving cost here is *huge*.
Though, PRs that are also changing code but in subsequent updates only update
documentation, the CI can't tell those apart and will have to run the whole suite
again -- this is a disadvantage to having documentation as part of project source repo.
was (Author: rhusar):
The update to this is that we now manage documentation within the wildfly repo in master
branch, so any updates to the docs here do not need to run the whole CI -- problably only
some sort of 'doc lint'. Though, PRs that are also changing code but in subsequent
updates only update documentation, the CI can't tell those apart and will have to run
the whole suite again -- this is a disadvantage to having documentation as part of project
source repo.
Allow selective CI builds
-------------------------
Key: WFLY-5793
URL:
https://issues.jboss.org/browse/WFLY-5793
Project: WildFly
Issue Type: Task
Reporter: Ryan Emerson
Assignee: Ken Wills
Priority: Optional
Currently the testsuite is ran against all PRs regardless of which files are being
changed. This is waste of energy/resources when commits only contain changes that do not
effect code (e.g. when updating README.md).
A possible solution would be for a blacklist to be created, which lists the file types
which can be safely ignored by CI when a PR only contains changes to files of the listed
file types.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)