You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(blog): reader comments on CI/CD CloudHub post + inline code/link support
Add 16 preserved Wix reader comments (5 threads) to the GitHub Actions ->
CloudHub post as verbatim readerNotes, and build out the inline markup the
comments needed:
- ReaderNotes.astro: inlineSegments() parser turns `backtick` spans into
inline-code chips and bare URLs into autolinks (new tab + external icon).
URLs inside a code span stay literal (long Maven/Java error strings are
one unbroken chip). <Code> now passes dual github-light/dark themes so
reader-note code renders correctly in BOTH themes (was washed-out in light).
- CodeBlockEnhancer.astro: scope extended to .reader-note pre.astro-code so
those blocks get the header bar + Copy button (they render outside .prose).
- global.css: .reader-note code / .reader-note__link rules — wrapping chips
(overflow-wrap:anywhere + box-decoration-break:clone) and AA links
(--accent-strong + underline + focus ring).
- Bump .claude submodule (reader-note conventions + add-post skill).
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: src/content/blog/how-to-set-up-a-ci-cd-pipeline-to-deploy-your-mulesoft-apps-to-cloudhub-using-github-actions.mdx
Thank you so much for your video and intruduction!
16
+
I sucessfully deployed with cloudhub2 branch's codes.
17
+
And now trying your main branch's.
18
+
19
+
Firstly, Action failed on deploy step with 401 code.
20
+
I find that you have nexus-ee auth info(action secret) in `.maven/setting.xml`, but I donnot have.
21
+
So,
22
+
I tried not to deploy with nexus-ee dependencies.
23
+
I delete profiles contents in `setting.xml` and tried again.
24
+
but failed with this error
25
+
`org.mule.maven.client.api.BundleDependenciesResolutionException: org.eclipse.aether.resolution.ArtifactResolutionException: com.github.everit-org.json-schema:org.everit.json.schema:jar:1.12.2 was not found in https://maven.anypoint.mulesoft.com/api/v3/maven during a previous attempt. This failure was cached in the local repository and resolution is not reattempted until the update interval of anypoint-exchange-v3 has elapsed or updates are forced`
26
+
27
+
I asked chatgpt sensei with this error, he asked me to import nexus-ee dependencies...
28
+
29
+
could you please tell me what should I do with this?
30
+
- author: "Alex Martinez"
31
+
replyTo: "Young Mitchell"
32
+
date: 2025-04-10
33
+
text: "If you try the main branch, you actually do need nexus credentials because of the MUnit tests :("
34
+
- author: "Kati Sarajärvi"
35
+
date: 2024-04-30
36
+
text: "I am unable to make the versioning work. I can to run the pipeline and get the application running in Runtime manager, but pushing new updates to main does not work. I have to delete the running app and only then can I run the pipeline successfully again, Is this a featrure or a bug?"
37
+
- author: "Alex Martinez"
38
+
replyTo: "Kati Sarajärvi"
39
+
date: 2024-04-30
40
+
text: "could you please share the error you're getting?"
41
+
- author: "willian souza vieira"
42
+
date: 2023-12-20
43
+
text: "I´m getting this error `Error: Failed to execute goal org.mule.tools.maven:mule-maven-plugin:3.8.2:deploy (default-deploy) on project salesforce-to-twilid: Deployment configuration is not valid, : No deployment configuration was defined. Aborting. -> [Help 1]`"
44
+
- author: "Alex Martinez"
45
+
replyTo: "willian souza vieira"
46
+
date: 2023-12-21
47
+
text: |-
48
+
Hello! You're missing the configuration in your `pom.xml` - at the beginning of the post it states the following:
49
+
50
+
We won't go into the details of creating a GitHub repo with your Mule application. You can take a look at the example repo we'll be using throughout the post so we can focus on explaining the CI/CD setup.
51
+
52
+
Please take a look at the repo: https://github.com/alexandramartinez/github-actions
53
+
54
+
You should configure something like this:
55
+
code: |-
56
+
<configuration>
57
+
<cloudHubDeployment>
58
+
<uri>https://anypoint.mulesoft.com</uri>
59
+
<muleVersion>${app.runtime}</muleVersion>
60
+
<username>${anypoint.username}</username>
61
+
<password>${anypoint.password}</password>
62
+
<applicationName>${app.name}</applicationName>
63
+
<environment>${env}</environment>
64
+
<workerType>MICRO</workerType>
65
+
<region>us-east-2</region>
66
+
<workers>1</workers>
67
+
<objectStoreV2>true</objectStoreV2>
68
+
</cloudHubDeployment>
69
+
<classifier>mule-application</classifier>
70
+
</configuration>
71
+
lang: "xml"
72
+
- author: "willian souza vieira"
73
+
replyTo: "Alex Martinez"
74
+
date: 2023-12-21
75
+
text: "Ok thanks for reply, it worked now : D"
76
+
- author: "Julian Redwood"
77
+
date: 2023-07-27
78
+
text: |-
79
+
Hi Alex, I tried to implement the workflow but I'm getting an error on "Build with MAven" section
80
+
81
+
"`Error: Failed to execute goal on project <projectname>: Could not resolve dependencies for project com.mycompany:projectname:mule-application:1.0.0-SNAPSHOT: Failed to collect dependencies at <> Failed to read artifact descriptor for 4<> Could not transfer artifact <> from/to anypoint-exchange-v3 (https://maven.anypoint.mulesoft.com/api/v3/maven): authentication failed for https://maven.anypoint.mulesoft.com/api/v3/<>, status: 401 Unauthorized -> [Help 1]`"
82
+
83
+
Any idea why?
84
+
85
+
Thank you
86
+
- author: "Alex Martinez"
87
+
replyTo: "Julian Redwood"
88
+
date: 2023-07-27
89
+
text: |-
90
+
Hi Julian! Make sure you're not using MFA and you're using the correct Anypoint Platform credentials (username/password).
91
+
92
+
You can also contact me if you're still having issues so we can troubleshoot together :)
93
+
- author: "Julian Redwood"
94
+
replyTo: "Alex Martinez"
95
+
date: 2023-07-28
96
+
text: "I ended up making the API spec public and that worked ok - not ideal but will get me over the line. Thank you and great set of videos/blogs."
97
+
- author: "Alex Martinez"
98
+
replyTo: "Julian Redwood"
99
+
date: 2023-07-28
100
+
text: "Ohh! Well, this project did not include the API spec. I'll try to play around with that in the future to understand better how that works. I'm glad you found a workaround at least!"
101
+
- author: "Wuilver Patricio"
102
+
date: 2023-03-08
103
+
text: |-
104
+
¿Te funciona con la version actual de maven (`3.9.0`) que tiene el sistema operativo (ubuntu)?
105
+
Porque a mi no. Esto según entiendo es porque las versiones soportadas por mule maven plugin son de `3.6.3` a `3.8.6` (Mule Maven Plugin 3.8.0 Release Notes | MuleSoft Documentation)
106
+
- author: "Alex Martinez"
107
+
replyTo: "Wuilver Patricio"
108
+
date: 2023-03-08
109
+
text: |-
110
+
Puedes revisar el repositorio directamente para ver si hay algo diferente con tu proyecto. Pero a mí sí me funciona perfecto siguiendo las instrucciones de los posts.
111
+
112
+
Si lo intento correr localmente, yo estoy en Mac, mi maven es `3.8.4` y mi java es `8`. Pero si lo intentas correr desde GitHub Actions, no importa tu sistema operativo, simplemente se basa en lo que está en el `build.yml`
113
+
114
+
Avísame si esto contestó tu pregunta
115
+
- author: "Wuilver Patricio"
116
+
replyTo: "Alex Martinez"
117
+
date: 2023-03-09
118
+
text: "Todo parece indicar que depende de la imagen que cargue el runner, la version de maven no siempre es la misma, por lo que la ejecución falla aleatoriamente, lo que hice fue establecer una versión especifica en un paso del flujo de trabajo."
119
+
- author: "Alex Martinez"
120
+
replyTo: "Wuilver Patricio"
121
+
date: 2023-03-09
122
+
text: "Puedes postear aqui lo que agregaste en caso de que otras personas tengan el mismo problema?"
123
+
- author: "Wuilver Patricio"
124
+
replyTo: "Alex Martinez"
125
+
date: 2023-03-09
126
+
text: |-
127
+
Con lo cual se establece Apache Maven `3.6.3`, hice pruebas sobre el runner Ubuntu en las versiones soportadas por github-actions.
128
+
129
+
Y ya hay documentación del incidente:
130
+
Missing BasicRepositoryConnectorFactory With New Version of Apache Maven (3.9.0) | MuleSoft Help Center
131
+
code: |-
132
+
- name: "Setup maven"
133
+
run: |
134
+
sudo apt-get install maven
135
+
mvn -v
136
+
lang: "yaml"
137
+
- author: "Alex Martinez"
138
+
replyTo: "Wuilver Patricio"
139
+
date: 2023-03-10
140
+
text: "Muchas gracias!!"
10
141
---
11
142
12
143
Creating CI/CD (Continuous Integration, Continuous Delivery) pipelines for your code has become a standard practice. Instead of worrying about deployments and keeping your environments up to date, you can set up this automated pipeline to do the deployments for you. You can focus on developing your code and let the pipeline take care of the rest.
0 commit comments