EGit timeout with TALEND - timeout

I have trouble with Egit plugin under talend. When pushing, it fails with message timeout exceeded 30 000ms. Under eclipse, there is a menu team where I can change the timeout value, but talend doesn't have this. How can this value be changed under talend. Thank's for your help.

Related

Jira integration with Bitbucket: sync does not work

We setup the integration of Jira Server with Bitbucket Cloud according to the Connect Bitbucket Cloud to Jira Software Server
The repos were added successfully. But no futher sync performs afterwards.
We tried everything in doc Fix error connections between Jira Cloud and Bitbucket and these did not help.
The sync state is hanging forever: image
The clicking on sync button does not work (either by hands or automatically).
This issue looks like a bug since there are no ERROR or WARN messages in atlassian-jira.log file concerning this issue (we switched the following log appenders into DEBUG level: com.atlassian.jira.plugins.dvcs, com.atlassian.jira.plugins.dvcs.scheduler, com.atlassian.jira.plugins.dvcs.spi.bitbucket, com.atlassian.jira.plugins.dvcs.spi.bitbucket.BitbucketCommunicator).
So it looks like the sync works ok but it does not.
How can we fix the sync?
The problem was solved (partially I suppose) by restarting Jira server.
The possible reason is in leaking http connection in Apache HttpClient.

Is it possible to update google dataflow job with a new pipeline?

I am trying to add a new independent pipeline to running job, and it keeps failing. Also it fails quite ungracefully, sitting in a "-" state for a long time before moving to "not started" and then failed with no errors reported.
I suspect that this may be impossible, but I cannot find confirmation anywhere.
Job id for the latest attempt is 2016-02-02_02_08_52-5813673121185917804 (it's still sitting at not started)
Update: It should now be possible to add a PubSub source when updating a pipeline.
Original Response:
Thanks for reporting this problem. We have identified an issue when updating a pipeline with additional PubSub sources.
For the time being we suggest either running a new (separate) pipeline with the additional PubSub source, or stopping and starting the job over with the additional sources installed from the beginning.

Workflow action not executed in Jira Issue Updater plugin

So currently I am trying to progress my JIRA workflow with the Jira Issue Updater plugin in Jenkins. Attached are my config screenshot and my workflow. However i get this error when I execute a commit triggered build.
JIRA Update Results Recorder
Unable to connect to REST service
java.io.IOException: Server returned HTTP response code: 400 for URL: http://*******:9055/rest/api/2/search?jqlFinished: SUCCESS
This does not have any effect on my Jira workflow.
Thanks for the help in advance and let me know if more information is needed.
Hadi
EDIT: I got a 404 meaning the JQL is incorrect, but when I try to use that in incognito mode I get an empty string, However, if i am locally logged in, I get all issues in xml format.
Workflow
Jenkins Jira Config
I ended up using the JIRA plugin instead.
I used Progress JIRA Issues by workflow action step after build successful phase.
Attaching a screenshot of the configuration.
I am still trying to figure how to pull the issue number from the commit message for this action.
JIRA PLUGIN CONFIG
This is a following question and answer if anybody else gets stuck:
How can I get JIRA issue number from a commit message in Jenkins

Dataflow job fails, but the step still shows successful

Our pipeline failed, but the graph in the developers console still shows it as been successful. However, the results were not written to BigQuery, and the job log clearly shows it failed.
Shouldn't the graph show it as failed too?
Another example:
Another example:
This was a bug with the handling of BigQuery outputs that was fixed in a release of the Dataflow service. Thank you for your patience.

TFS 2013 Report error

We have a whole bunch of reports sitting in TFS 2010, then we decide to directly upgrade to TFS 2013.
Upgrading and configuration and have been done successfully.
However those old reports are not working, I fixed the data source connection string and rebuild the data warehouse successfully.
But I get the error:
An error has occurred during report processing. (rsProcessingAborted)
Query execution failed for dataset 'IterationParam'. (rsErrorExecutingCommand)
The dimension '[Iteration]' was not found in the cube when the string, [Iteration].[Parent_ID].[XXX], was parsed.
I looked in the analysis service database and could not find Itration Dimension.
Is something wrong? Please give me advice
cheers,
Did you rebuild just the warehouse, or the cube also? You need to do both. And you need to rebuild the warehouse first, then the cube afterwards.
I use the TFS Web Services to do this:
Fire up the web service page, for me its: http://localhost:8080/tfs/TeamFoundation/Administration/v3.0/WarehouseControlService.asmx
Execute GetProcessingStatus passing false for the includeOnlineHostsOnly
Make sure that all the jobs are currently Idle
Execute ProcessWarehouse leaving the args blank
Rerun GetProcessingStatus until all the warehouse jobs are idle again
Execute ProcessAnalysisDatabase passing in Full for the processingType
Rerun GetProcessingStatus until all the jobs are idle again

Resources