Double emails sent from Jenkins - jenkins-plugins

i have configured email-ext and it work ok. Then i install Build flow plug-in and configure some jobs. It Works but Send me 2 emails after completed.
For test i create new Build flow job and in it i Build one job. Then on post Build actions i configure email-ext for sucess and receive 2 emails. Can anyone help mi with this? Below i send logs from Build flow job
Started by user Dawid Wybierek
[EnvInject] - Loading node environment variables.
Building on master in workspace C:\Users\poca\.jenkins\workspace\testy\Test flow
No emails were triggered.
Schedule job testy » Test email
Build testy » Test email #2 started
testy » Test email #2 completed
Email was triggered for: Success
Sending email for trigger: Success
Sending email to: dawid.wybierek#***.com
Email was triggered for: Success
Sending email for trigger: Success
Sending email to: dawid.wybierek#***.com
Finished: Success
config :
screen from email ext

Related

Unable to run test in Flow Designer

I am going through MuleSoft's "Development Fundamentals (Mule 4)" and I'm doing one of the walkthroughs - "WT 2-3: Create an integration application with Flow Designer that consumes an API" and on one of the steps (step 23) the test button does not run and consequently, I can't test the REST endpoint, because I don't have a URL to send requests to.
When I click the Test button, it switches to "Refresh" and on the left of the button it says "Project needs to be refreshed".
However, when I click the Refresh button and wait several minutes for the refresh, it goes back to the Test button, which again doesn't work and shows "Project needs to be refreshed" when clicked, so I am stuck in this endless loop.
I tried deleting everything I had done up to that point and started again from scratch, but when I reached that walkthrough again, I had the same problem.
The only things I have in the Flow Designer are an HTTP Listener and "American Flights API". The problem occurs after I add the API. Before I added in the API, I successfully ran the test with an HTTP Listener and a logger.
The HTTP Listener configuration:
path : flights
The "American Flights API" configuration:
host : training4-american-api.cloudhub.io
port : 80
base path : /
protocol : HTTP
The log in the Runtime Manager shows a LifecycleException, but I don't know what is causing it or how to prevent it.
Here is the log from the Runtime Manager:
[2021-08-22 14:56:32.872] INFO com.mulesoft.ch.queue.boot.PersistentQueueCoreExtension [qtp1112210076-38]: The PersistentQueueManager is NOT configured. The normal VM queue manager will be used.
[2021-08-22 14:56:40.483] INFO org.mule.runtime.api.el.AbstractBindingContextBuilderFactory [qtp1112210076-38]: Loaded BindingContextBuilderFactory implementation 'org.mule.runtime.core.api.el.DefaultBindingContextBuilderFactory' from classloader 'org.mule.runtime.module.reboot.internal.MuleContainerSystemClassLoader#740e48c1'
[2021-08-22 14:56:40.874] INFO org.mule.runtime.core.internal.util.journal.TransactionJournal [qtp1112210076-38]: Using files for tx logs /opt/mule/mule-4.3.0/./.mule/americanflightsapp-xslg/queue-tx-log/tx1.log and /opt/mule/mule-4.3.0/./.mule/americanflightsapp-xslg/queue-tx-log/tx2.log
[2021-08-22 14:56:40.882] INFO org.mule.runtime.core.internal.util.journal.TransactionJournal [qtp1112210076-38]: Using files for tx logs /opt/mule/mule-4.3.0/./.mule/americanflightsapp-xslg/queue-xa-tx-log/tx1.log and /opt/mule/mule-4.3.0/./.mule/americanflightsapp-xslg/queue-xa-tx-log/tx2.log
[2021-08-22 14:56:41.137] INFO com.mulesoft.ch.batch.BatchCoreExtension [qtp1112210076-38]: Persistent queues is not enabled for batch module as it was not configured in Cloudhub console
[2021-08-22 14:56:41.168] INFO org.mule.runtime.core.internal.util.queue.QueueXaResourceManager [ArtifactDeployer.start.01]: Starting ResourceManager
[2021-08-22 14:56:41.169] INFO org.mule.runtime.core.internal.util.queue.QueueXaResourceManager [ArtifactDeployer.start.01]: Started ResourceManager
[2021-08-22 14:56:41.207] INFO org.mule.runtime.core.internal.logging.LogUtil [ArtifactDeployer.start.01]:
**********************************************************************
* Application: americanflightsapp-xslg *
* OS encoding: UTF-8, Mule encoding: UTF-8 *
* *
**********************************************************************
[2021-08-22 14:59:47.852] INFO org.mule.runtime.core.internal.util.queue.QueueXaResourceManager [qtp1112210076-39]: Stopping ResourceManager
[2021-08-22 14:59:47.852] INFO org.mule.runtime.core.internal.util.queue.QueueXaResourceManager [qtp1112210076-39]: Stopped ResourceManager
[2021-08-22 14:59:47.867] INFO org.mule.runtime.core.internal.lifecycle.RegistryLifecycleCallback [qtp1112210076-39]: Failure executing phase stop over object DefaultBatchEngine, error is: org.mule.runtime.api.lifecycle.LifecycleException(Failed to invoke lifecycle phase "stop" on object: com.mulesoft.mule.runtime.module.batch.internal.engine.DefaultBatchEngine#2fd96fde)
[2021-08-22 14:59:47.869] INFO org.mule.runtime.module.deployment.impl.internal.artifact.AbstractDeployableArtifact [qtp1112210076-39]: Stopping app 'americanflightsapp-xslg' with no mule context
[2021-08-22 14:59:47.922] INFO org.mule.runtime.core.internal.logging.LogUtil [qtp1112210076-39]:
**********************************************************************
* Application "americanflightsapp-xslg" shut down normally on: *
* 8/22/21 2:59 PM *
* Up for: 0 days, 0 hours, 3 mins, 6.753 sec *
**********************************************************************
Any help is welcome, thank you.
The problem was coming from MuleSoft's side. I reported the problem on their Help Center and got a response that the issue was under investigation. Several days later, the problem was fixed and the Test button on the Flow Designer page is now working correctly.

firebase deploy is slow and not responding

Running the deploy command to a site just makes the Terminal blink as if it was stuck in some heavy operation.
And nothing would happen. I actually didn't try running with the --debug flag.
First thought is that I'm behind a company proxy. So I setup a "pure" connection and it's still not connecting. So what is the problem?
Open the firebase-debug.log file it contains the logs you may find an error in there.
logs similar to this
[debug] [2020-09-26T07:53:15.852Z] > command requires scopes: ["email","openid","https://www.googleapis.com/auth/cloudplatformprojects.readonly","https://www.googleapis.com/auth/firebase","https://www.googleapis.com/auth/cloud-platform"]
[debug] [2020-09-26T07:53:15.854Z] > authorizing via signed-in user
[debug] [2020-09-26T07:53:15.855Z] [iam] checking project testproject for permissions ["firebase.projects.get","firebasehosting.sites.update"]
[debug] [2020-09-26T07:53:15.861Z] > refreshing access token with scopes: ["email","https://www.googleapis.com/auth/cloud-platform","https://www.googleapis.com/auth/cloudplatformprojects.readonly","https://www.googleapis.com/auth/firebase","openid"]
[debug] [2020-09-26T07:53:15.861Z] >>> HTTP REQUEST POST https://www.googleapis.com/oauth2/v3/token
In my case, it was due to a slow internet connection thus connection could not be established.
Running firebase --help there should be an info popping up if there is an update available.
If it is you should update and then deploy again.
npm update -g firebase-tools
firebase deploy
If that isn't working, list the projects and check if you are logged in
firebase list
firebase login

Error message "You do not have permission to modify this app" from a Google App Engine deployment

I am following the instructions on http://beta.appinventor.mit.edu/learn/reference/other/tinywebdb.html , trying to create a custom TinyWebDB for a grade 10 class I teach. After creating a new Project (the instructions say create an Application, but I only see a Create a new project button), I change the project name in the local file app.yaml file, load it in, and click on Deploy. I get the following error message:
Starting update of app: npicswebdb, version: 1
01:35 PM Getting current resource limits.
2016-03-09 13:35:26,727 ERROR appcfg.py:2396 An error occurred processing file '': HTTP Error 403: Forbidden Unexpected HTTP status 403. Aborting.
Error 403: --- begin server output ---
You do not have permission to modify this app (app_id=u's~npicswebdb').
--- end server output ---
2016-03-09 13:35:26 (Process exited with code 1)
Is there some way I need to log in to the App Engine Launcher so it connects with my App Engine in the cloud? There is nothing in the instructions about doing that, and I don't see any way to do that in the launcher.
Thanks for your help.
Try adding "--no_cookies":
appcfg.py -A projectname update app.yaml --no_cookies
Delete cookie file something like this: ~/.appcfg_oauth2_tokens_java.
Re-run your command, it will prompt to login from browser and copy-paste a token back to the terminal.
Similar to the other answers. I run into the same issue and removing those stored credentials helped me, i.e:
rm ~/.appcfg_oauth2_tokens_java
rm ~/.appcfg_cookies
Found more details here: IT Code Hub - AppEngine deployment

Google app engine launcher: Invalid username or password

I've download google app engine (python) for windows and install it. Then I went to console.developers.google.com/project and create new project. After that, I launched google app engine launcher, create new application and named it as project I have recently create. I click on deploy and constantly getting this error:
03:35 PM Application: udacity-hello-pozdrav; version: 1
03:35 PM Host: appengine.google.com
03:35 PM
Starting update of app: udacity-hello-pozdrav, version: 1
03:35 PM Getting current resource limits.
Password for t******.****#gmail.com: Invalid username or password.
2014-09-06 15:35:56,690 ERROR appcfg.py:2411 An error occurred processing file '': HTTP Error 401: Unauthorized. Aborting.
Error 401: --- begin server output ---
Must authenticate first.
--- end server output ---
2014-09-06 15:35:56 (Process exited with code 1)
You can close this window now.
I've read about appcfg.py but when I enter it in cmd, It says that it's not recognized.
Would be much better if you will use appcfg.py with --oauth2 flag.
Like appcfg.py --oauth2 update /path/to/your/app.
For the first time you will see the browser window where you'll need to allow access to your account. Then you can deploy without entering any credentials and without confirmations. This will work even with 2-step authentication turned on.
The "Invalid username or password" error is due to Google security protection. To overcome this error message and be able to deploy from the Launcher, go to your Google Account Settings, then enable "Access for Less Secure Apps" under Security Check Up.

Glide/Gaelyk/Groovy: Error deploying to Google App Engine: Can’t enter oauth2 token

As part of the deployment process of a Glide project (http://glide-gae.appspot.com/docs/intro step 3 of 2nd section) you need to authenticate using oauth2. My browser popped up with the token as expected but the process didn’t wait for me to copy the code in, it just carried on with the following error...
22:30:12.713 [DEBUG] [org.gradle.launcher.daemon.server.DaemonStateCoordinator] Daemon is busy, sleeping until state changes.
22:30:12.733 [INFO] [org.gradle.launcher.daemon.server.exec.LogToClient] About to start relaying all logs to the client via the connection.
22:30:12.734 [INFO] [org.gradle.launcher.daemon.server.exec.LogToClient] The client will now receive all logging from the daemon (pid: 12557). The daemon log file: /.gradle/daemon/1.8/daemon-12557.out.log
22:30:12.739 [DEBUG] [org.gradle.launcher.daemon.server.SynchronizedDispatchConnection] thread 14: received class org.gradle.launcher.daemon.protocol.CloseInput
22:30:12.740 [DEBUG] [org.gradle.launcher.daemon.server.DefaultDaemonConnection] Received IO message from client: CloseInput[id=069864b2-2948-4a9d-abea-0705274136a1.2]
22:30:12.741 [INFO] [org.gradle.launcher.daemon.server.exec.ForwardClientInput] Closing daemon's stdin at end of input.
22:30:12.742 [INFO] [org.gradle.launcher.daemon.server.exec.ForwardClientInput] The daemon will no longer process any standard input.
22:30:12.747 [INFO] [org.gradle.launcher.daemon.server.exec.ExecuteBuild] Executing build with daemon context: DefaultDaemonContext[uid=3901cff0-8d50-41b6-9459-e31f7b78f1e3,javaHome=/Library/Java/JavaVirtualMachines/jdk1.7.0_51.jdk/Contents/Home,daemonRegistryDir=.gradle/daemon,pid=12557,idleTimeout=10800000,daemonOpts=-XX:MaxPermSize=256m,-Xmx512m,-Dfile.encoding=UTF-8]
Please enter code: Encountered a problem: No line found
Please see the logs [/var/folders/c8/vx2jf50j68x1z3_pysy6kxjm0000gp/T/appcfg2389447403250678065.log] for further information.
Daemon vm is shutting down... The daemon has exited normally or was terminated in response to a user interrupt.
----- End of the daemon log -----
org.gradle.tooling.GradleConnectionException: Could not execute build using Gradle distribution 'http://services.gradle.org/distributions/gradle-1.8-bin.zip'.
What can I do to be able to deploy my application? How can I force the process to wait for me to enter the code?
If that's (glide deploy) not working for you, the easiest option is to export the app as a standard gradle project and then execute the gaeUpdate task.
glide -a somedir/yourapp -o where/you/want/to/export/app export
Note that the export is command at the end, -o tell the location where it should be exported.
Then from the exported project run: gradle gaeUpdate
A work around is to manually set your credentials in the GAE build.gradle file.
Update the following file:
/glide/install/generated/app-name/build.gradle
appcfg {
email = ‘email-address'
password = ‘password'
app {
id = ‘app-id'
}
}
This means that the values from the __glide.groovy file are ignored, but at least you can get the application deployed

Resources