Learn about the new Oracle AI Agent Studio for Fusion Applications: Watch Now
Progress with Redwood: Redwood Resources for Oracle Cloud HCM - Go Here
Progress with Redwood: Redwood Resources for Oracle Cloud HCM - Go Here
To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered. (newly added) Please note that it is also important to respond to EACH comment your question receives. Your Yes or No response ensures an accurate status for your question.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
Publish Changes does not kick off pipeline
Summary:
Is the build executor supposed to start automatically?
Content (please ensure you mask any confidential information):
I have published my first small extension. In VB Studio, in the Git tab, I can see that my changes were committed to my local main branch. My local main branch shows the date that I published, and it shows the description I had entered for my change. Unfortunately, it did not kick off my default pipeline consisting of the two jobs to package and deploy my extension. My package job is configured to Automatically perform build on SCM commit. I checked the pipeline, the jobs, and the environment, but nothing shows up there. I checked the build executor and
Tagged:
1